Skip to content

Make it easier to set things up for attach. #1380

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

Closed
ericsnowcurrently opened this issue Apr 12, 2018 · 2 comments
Closed

Make it easier to set things up for attach. #1380

ericsnowcurrently opened this issue Apr 12, 2018 · 2 comments
Labels
area-debugging feature-request Request for new features or functionality

Comments

@ericsnowcurrently
Copy link

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."
  • a "set up for attach" UI element
  • a "set up" checkbox/button/link in the attach UI element (see Add a UI element to make "attach" easier. #1378)
  • a "launch-detached" or "launch-attached" launch config
    • auto-add a launch config that attaches to that debugger
  • a registry of known "attachable" processes? (or discovery of such)
  • extension config options for supported hosts/ports (or hosts/PIDs)

Environment data

  • VS Code version: 1.22.1
  • Extension version (available under the Extensions sidebar): 2018.3.1
  • OS and version: Ubuntu 16.04
  • Python version (& distribution if applicable, e.g. Anaconda): n/a
  • Type of virtual environment used (N/A | venv | virtualenv | conda | ...): n/a
  • Relevant/affected Python packages and their versions: n/a

Actual behavior

see above

Expected behavior

see above

Steps to reproduce:

n/a

Logs

n/a

@DonJayamanne
Copy link

@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.

@brettcannon
Copy link
Member

Yes, this all requires a spec from @qubitron and I think the current plan is to tackle SSH first.

@lock lock bot locked as resolved and limited conversation to collaborators Oct 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
area-debugging feature-request Request for new features or functionality
Projects
None yet
Development

No branches or pull requests

3 participants