Closed geeksville closed 1 year ago
note: I'm talking about the vscode deployment of the python dev version of the code (which gets copied by the vscode runpydeck task:
"command": "ssh deck@${config:deckip} -p ${config:deckport} ${config:deckkey} 'export PLUGIN_PATH=${config:deckdir}/homebrew/dev/plugins; export CHOWN_PLUGIN_PATH=0; export LOG_LEVEL=DEBUG; cd ${config:deckdir}/homebrew/services; echo '${config:deckpass}' | sudo -SE python3 ${config:deckdir}/homebrew/dev/pluginloader/backend/main.py'",
In that case it is running straight .py files that were sshed over by the developer. and the directory is .../homebrew/dev....
Please confirm
Bug Report Description
I just tried building and installing decky-loader myself for the first time (so I could add some debugging code). I used the vscode "allinone" task and it builds/installs/seems to run.
But when I go install from the store I see:
The problem is that the plugin directory isn't being set correctly in plugin.py. The code there says:
BUT plugin/decky_plugin is in /home/deck/homebrew/dev/pluginloader not
/home/deck/homebrew/dev/pluginloader/backend
So my nasty hack is to stick in a .. after the backend directoy and we then the loader gets launched with the correct options to let it find decky_loader in the python path.
Though clearly I'd expect this is not a good fix because I assume it would then have the wrong path for production. @TrainDoctor Any advice? If not I'll look for a clean fix.
Expected Behaviour
decky_loader should be found in the python path.
SteamOS version
3.4.4 stable
Selected Update Channel
Stable
Have you modified the read-only filesystem at any point?
No response
Logs
debug log attached above (since I was running in dev mode the log output only comes in vscode)