Python API refuses to use `$HOME/.simvue.toml` and `simvue.toml` in current directory

[alahiff]

When trying to run simvue_sender as a cron, the Python API ignores my .simvue.toml in $HOME and simvue.toml in $HOME, but instead decided to pick /lustre/home/alahiff/Simvue/execution/2024-12-06/simvue.toml which I had forgotten I had. Note that before running simvue_sender my script changed directory to $HOME, so even if it ignored .simvue.toml it should have seen simvue.toml in the current directory.

Note this doesn't happen when running manually but only as a cron.

[alahiff]

In order to get the client to work I need to hack simvue/config/user.py, i.e. hardwire the location of $HOME/.simvue.toml.

[wk9874]

So current code for finding a simvue.toml file is:

That feels very wrong... It means that it will recursively look through the users home directory and all subdirectories before checking the $HOME directory.

What do we expect this code to do @kzscisoft @alahiff ? I always thought it just checked the base level current working directory (ie, not any subdirectories), and then checks the home directory...

The current implementation means simvue would probably take a terrifyingly long time to startup if running on a HPC or cluster with a lot of files in the user's workspace...

[wk9874]

I assume this is causing Andrew's issue - it is looking through his entire home directory (not top down, so not in any order) and happens to find the toml file in /lustre/home/alahiff/Simvue/execution/2024-12-06/simvue.toml before it finds one at the base level of current working dir (and before it checks home)

[alahiff]

Yes, this definitely has to go! I can't think of any reason why this would be needed.