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
In #1379 I brought up ways that attach needs more clarity. One question is what needs to be set up first in order to attach. For localhost, connecting to a "pristine" PID (if that were supported) wouldn't require any extra set up. However, just about every other case of attach would. Here are some possible mechanisms:
ssh
some other remote daemon we provide (exposing https, for instance)
launch-detached
launch-attached
As far as I can tell, the extension does not provide a clear way to set things up, such that the user could then attach. Some ideas:
alert, console msg, etc.: "Run this script on the target host to enable attaching the debugger."
@ericsnowcurrently@brettcannon@qubitron
Is this issue resolved? I think we need to break this down into specific items. This was initially filed as a brain dump, now we need to review the concerns and create separate issues for each if necessary.
In #1379 I brought up ways that
attach
needs more clarity. One question is what needs to be set up first in order to attach. For localhost, connecting to a "pristine" PID (if that were supported) wouldn't require any extra set up. However, just about every other case ofattach
would. Here are some possible mechanisms:As far as I can tell, the extension does not provide a clear way to set things up, such that the user could then attach. Some ideas:
attach
UI element (see Add a UI element to make "attach" easier. #1378)Environment data
Actual behavior
see above
Expected behavior
see above
Steps to reproduce:
n/a
Logs
n/a
The text was updated successfully, but these errors were encountered: