Running Commands on Remote Development Host Fails

Describe the bug Running Doki theme installation/sticker&bg removal commands fail when working via remote development.

I’m fairly new to VSCode but it seems that Doki must be installed on both local and remote hosts for the theming to work properly - Themed CSS appear to not load when Doki Theme is not installed on the remote host.

A workaround is to simply run the commands on a non-remote window then command palette -> Reload Window

To Reproduce

1. Install fresh VSCode for Mac and the Remote-SSH (v0.84.0) extension
2. Set up SSH host and connect
3. Install Doki-Theme (v84.1.6) on both local and remote hosts
4. Command Palette -> >Doki-Theme: Install Vanilla's Sticker (etc)
5. Follow the sudo chmod instructions in the Asset Installation Help (etc) window
6. Repeat >Doki-Theme: Install Vanilla's Sticker (etc)

Expected Behavior

• Running the same command after following the chmod instructions should work.
• Should be able to run these commands in the remotely connected window.

Environment Version: 1.69.2 (Universal) Commit: 3b889b090b5ad5793f524b5d1d39fda662b96a2a Date: 2022-07-18T16:12:57.074Z (2 wks ago) Electron: 18.3.5 Chromium: 100.0.4896.160 Node.js: 16.13.2 V8: 10.0.139.17-electron.0 OS: Darwin arm64 21.4.0

Doki-Theme (v84.1.6)

Logs This seems to be the only log with a stacktrace, but I can provide other logs if needed. window.log

Note Perhaps related to https://github.com/doki-theme/doki-theme-vscode/issues/164

[Unthrottled]

However, if that’s the case I think for usability purposes it might be nice if the helper tab that gets opened up can either detect it’s in a remote environment and show an appropriately tailored helper tab, or to include said information in the current set of helper tabs. (Something like “Hey, I think you’re trying to run me in a remote context which won’t work! Please try again in a local context.” etc)

I’ll include something that calls out the SSH connection explicitly. This plugin should work if running on a code server, but I don’t think the SSH connection is the same (I can investigate more when I work #164 ).

So you can leave this open, I’ll close it when I’ve added this to the help menu.

Thanks for providing helpful debugging information!

[remiscarlet]

If the behavior of needing to run the commands on a local environment is intended, then I’d say that’s okay! (As opposed to somehow being able to pass those commands back to a local env context)

However, if that’s the case I think for usability purposes it might be nice if the helper tab that gets opened up can either detect it’s in a remote environment and show an appropriately tailored helper tab, or to include said information in the current set of helper tabs. (Something like “Hey, I think you’re trying to run me in a remote context which won’t work! Please try again in a local context.” etc)

Either way, I appreciate the helpful info and context! And thank you for the ffmpeg tip as well! I always forget how powerful ffmpeg is 😅

Finally, would it be better for this issue to be closed and to reopen with a feature request for the above or just keep it as is?