ppigazzini

I just installed msys2 in a sandbox with the latest official installer, the path is not updated automatically and there is not an option. The user can add "C:\msys64\usr\bin;C:\msys64\mingw64\bin;" in...

The standard module `winreg` is not an option because the msys2 installer (official and with choco) makes a nearly portable install and doesn't register the application under `HKEY_LOCAL_MACHINE\Software`. The `cmd...

In this case `where` works only if we ask the user to update the `PATH` (a viable option of course).

Check `where /?` to view all the options. It scanned all C: drive to find `grep.exe` ``` C:\Users\WDAGUtilityAccount>where /R C:\ grep.exe C:\msys64\usr\bin\grep.exe ``` Another option: we use a `worker.cmd` launcher...

> > Another option: we use a worker.cmd launcher on windows, the user doesn't need to update the PATH > > What do we set the path to though Standard...

Yes, the windows worker setup is meant for the CPU contributor not able to follow the installation tutorial on the wiki. Chocolatey has the plus to auto update msys2 after...

I need some time to study the changes of last couple of months (worker_info, schema check, runs collection etc), at the moment I don't know how to implement the feature...

This should be a good example https://github.com/glinscott/fishtest/pull/1256 but I need to understand the schema check in `fishtest/server/util.py`

IMO we shouldn't send a hostname. The field should be a totally optional user provided identifier that is shown next ~~or replace~~ the usual identifier in the GUI.

The hostname can be meaningless: workers running in different directories from the same host, workers started in colab, workers started in containers ecc. The user could not control the hostname:...