Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

shared debug sessions #3361

Open
akosyakov opened this issue Nov 1, 2018 · 1 comment
Open

shared debug sessions #3361

akosyakov opened this issue Nov 1, 2018 · 1 comment
Labels
debug issues that related to debug functionality enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility

Comments

@akosyakov
Copy link
Member

akosyakov commented Nov 1, 2018

Debug sessions should survive between user sessions. A user should be able to access all debug sessions running by the backend.

@akosyakov akosyakov added enhancement issues that are enhancements to current functionality - nice to haves debug issues that related to debug functionality labels Nov 1, 2018
@akosyakov akosyakov self-assigned this Nov 1, 2018
@akosyakov akosyakov added the vscode issues related to VSCode compatibility label Sep 19, 2019
@akosyakov
Copy link
Member Author

akosyakov commented Sep 19, 2019

That's important to implement to avoid loosing sessions on each reconnect. It will be quite straightforward for native extensions. But for VS Code extensions the debug process is forked from the plugin host process, so it would be gone on the reconnect. We need to make sure instead that even debug session from VS Code extensions are forked from the Theia backend process. cc @tolusha for shared remote sessions in Che then you will need to collect them somehow from the main Theia instance.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
debug issues that related to debug functionality enhancement issues that are enhancements to current functionality - nice to haves help wanted issues meant to be picked up, require help vscode issues related to VSCode compatibility
Projects
None yet
Development

No branches or pull requests

1 participant