You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The VSCode plugin for the local companion app / remote VSCode spawns a process that is not removed or cleaned up when the extension is subsequently uninstalled. Removal of the VSCode extension should also close the process.
For context, the original user feedback associated with this issue is:
The local companion doesn't seem to be removed when uninstalling the VSC extension.
I’m not sure I fully understand the feedback. As the VS Code Remote extension is a separate app / process to the companion app, so I don't think it makes sense for the two applications to be linked. For instance, a user may have the local companion app running for direct SSH access to their workspace, and not just for the VSCode extension.
Options/thoughts:
Currently, since the app is distributed as the binary file, we could investigate making the app more visible to users, by having a menu bar app (on OSX) or something similar.
Investigate methods of stopping the companion app, i.e after some amount of idle time.
EDIT: My fault, it seems this issue occurs during usage of the VSCode Extension, not the binary directly.
I’m not sure I fully understand the feedback. As the VS Code Remote extension is a separate app / process to the companion app, so I don't think it makes sense for the two applications to be linked. For instance, a user may have the local companion app running for direct SSH access to their workspace, and not just for the VSCode extension.
It is not really like that, sorry for confusion. VS Code Desktop is using own instance managed by Gitpod VS Code extension. It should not exist if Gitpod VS Code extension is uninstalled.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Activity
loujaybee commentedon Oct 8, 2021
For context, the original user feedback associated with this issue is:
I’m not sure I fully understand the feedback. As the VS Code Remote extension is a separate app / process to the companion app, so I don't think it makes sense for the two applications to be linked. For instance, a user may have the local companion app running for direct SSH access to their workspace, and not just for the VSCode extension.
Options/thoughts:
EDIT: My fault, it seems this issue occurs during usage of the VSCode Extension, not the binary directly.
akosyakov commentedon Oct 11, 2021
It is not really like that, sorry for confusion. VS Code Desktop is using own instance managed by Gitpod VS Code extension. It should not exist if Gitpod VS Code extension is uninstalled.
akosyakov commentedon Oct 11, 2021
+1 This we should do.
stale commentedon Jan 11, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
schickling commentedon Jan 12, 2022
Not stale.
stale commentedon Apr 14, 2022
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
schickling commentedon Apr 14, 2022
Still not stale.
loujaybee commentedon May 11, 2022
Should be addressed in: #8513
PR open: gitpod-io/openvscode-server#346