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

Enabling Debugging for Python Containers #89738

Closed
ucheNkadiCode opened this issue Jan 30, 2020 · 4 comments
Closed

Enabling Debugging for Python Containers #89738

ucheNkadiCode opened this issue Jan 30, 2020 · 4 comments
Assignees

Comments

@ucheNkadiCode
Copy link

ucheNkadiCode commented Jan 30, 2020

Scenario: Our goal is to allow our Python customers to debug and run a Python container with F5 using a launch task. Currently, the only way to debug a Python container is to launch the container separately and then remotely attach to an already running Python debugger. With the new feature we are proposing, we need the ability for our launch task to launch the container and the (newest version) Python debugger, then immediately attach the container to the volume mapped debugger successfully.

Issue: @haniamr has been attempting to create this experience, but each time he launches his container with the launch task and tries to start and attach to the Python debugger, the connection is refused, it fails, and exits. Unlike the Node or .NET debugger in VSCode, the Python debugger does not have retry logic implemented when a connection is unable to be established in a given time after a launch. This is a feature gap inhibits the aforementioned scenario and forces users like Hani to attempt to write their own retry logic or find a workaround. Two workarounds that have been found are to sleep for a few seconds which ensures the debugger will be ready to establish a connection or to look for a file that the debugger generates in the container when it's ready. Unfortunately, neither of these are long term solutions.

Proposal: Retry logic should be included as in-box feature within the Python Debugger.

@fiveisprime

@isidorn
Copy link
Contributor

isidorn commented Jan 31, 2020

This makes sense, however can you please file this against the python extension? Thank you https://github.com/microsoft/vscode-python

@isidorn isidorn closed this as completed Jan 31, 2020
@fiveisprime
Copy link
Member

@ucheNkadiCode this appears to already be tracked in the Python extension here: microsoft/vscode-python#7331

@ucheNkadiCode
Copy link
Author

ucheNkadiCode commented Feb 7, 2020

I see. @fiveisprime, this issue has been around since September of last year. With this new scenario that is aiming to enable users of Python (a very popular language) to debug with Docker (also widely used), I need this to be prioritized. Who can I get in contact to reprioritize this feature gap?

@fiveisprime
Copy link
Member

Seems like something Luciana and the Python team need to handle.

@vscodebot vscodebot bot locked and limited conversation to collaborators Mar 16, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants