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.

Sign up for GitHub

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

Jump to bottom

Make it possible to debug Theia plugins in sidecars #13249

Open
tsmaeder opened this issue Apr 26, 2019 · 4 comments
Open

Make it possible to debug Theia plugins in sidecars #13249

tsmaeder opened this issue Apr 26, 2019 · 4 comments
Labels
area/editor/theia Issues related to the che-theia IDE of Che lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.

Comments

@tsmaeder
Copy link
Contributor

Currently, we have no way to debug theia plugins running in a sidecar. I think we would need the following to make this work:

  1. Start the nodejs instance running the plugins host process in the sidecar with debug arguments. I would figure that we could use an environment variable defined in the workspace config to set the proper arguments.
  2. We need to make the debug port of the nodejs instance available from the outside. Maybe we need to do this manually via port forwarding?
  3. Document how to do this. This needs to be part of the "official" documentation.
@tsmaeder tsmaeder changed the title Make it possible to debug Theia plugins in Make it possible to debug Theia plugins in sidecars Apr 26, 2019
@tsmaeder tsmaeder mentioned this issue Apr 26, 2019
Closed
27 tasks
@tsmaeder
Copy link
Contributor Author

tsmaeder commented May 6, 2019

There is a description of how to run a theia/sidecar pair "by hand" in this document:

https://docs.google.com/document/d/1V292nYN655ekPPZvzdg7zbLpwVXW5uFjmffgoN2CmpM/edit#bookmark=id.kw179rb9gjl6

@tsmaeder tsmaeder mentioned this issue May 21, 2019
Closed
26 tasks
@tsmaeder tsmaeder added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Oct 22, 2019
@l0rd l0rd added team/ide2 severity/P1 Has a major impact to usage or development of the system. area/editor/theia Issues related to the che-theia IDE of Che and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Oct 23, 2019
@che-bot
Copy link
Contributor

che-bot commented Apr 22, 2020

Issues go stale after 180 days of inactivity. lifecycle/stale issues rot after an additional 7 days of inactivity and eventually close.

Mark the issue as fresh with /remove-lifecycle stale in a new comment.

If this issue is safe to close now please do so.

Moderators: Add lifecycle/frozen label to avoid stale mode.

@che-bot che-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Apr 22, 2020
@che-bot che-bot closed this as completed May 12, 2020
@tsmaeder tsmaeder reopened this May 12, 2020
@che-bot che-bot closed this as completed May 20, 2020
@tsmaeder
Copy link
Contributor Author

/lifecycle/frozen

@tsmaeder tsmaeder reopened this May 20, 2020
@tsmaeder tsmaeder added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels May 20, 2020
@tsmaeder tsmaeder mentioned this issue Jul 13, 2020
Merged
@tsmaeder
Copy link
Contributor Author

With the plugin host being nexe-compiled, this might be a bit more involved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/editor/theia Issues related to the che-theia IDE of Che lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. severity/P1 Has a major impact to usage or development of the system.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@nickboldt @l0rd @tsmaeder @che-bot