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

Insiders build: restarting debug sessions fails #3256

Closed
janosh opened this issue Jul 17, 2019 · 4 comments
Closed

Insiders build: restarting debug sessions fails #3256

janosh opened this issue Jul 17, 2019 · 4 comments

Comments

@janosh
Copy link
Contributor

janosh commented Jul 17, 2019

Environment data

  • VS Code version: 1.36.1
  • Extension version: Insiders
  • OS and version: macOS 10.14.5
  • Python version: 3.6.7 (miniconda)
  • Jedi or Language Server: latter

Expected behavior

When clicking the "Restart" button while debugging a code cell in the Python interactive window, I'd expect the debugger to reset state and jump back to line 1 of the cell.

Actual behavior

Clicking the "Restart" button just cancels the current debug session.

debug-restart-fails

@janosh janosh changed the title Insiders build: Insiders build: restarting debug sessions fails Jul 17, 2019
@greazer
Copy link
Member

greazer commented Jul 22, 2019

For now we don't have the resources to figure out how to fix this. It may not be possible with the current VSCode debugging architecture.

@greazer greazer closed this as completed Jul 22, 2019
@janosh
Copy link
Contributor Author

janosh commented Jul 22, 2019

@greazer If it's not too much trouble, could you briefly explain (for anyone who might revisit this issue in the future) what this hinges on? I.e. do you know which part of the debugging architecture is lacking?

@DonJayamanne
Copy link
Contributor

DonJayamanne commented Jul 23, 2019

Can I suggest we display an error indicating this feature isn't supported.
This way we know it's not a bug, instead it is by design.

@janosh
Copy link
Contributor Author

janosh commented Jul 26, 2019

@greazer I think it's worth reopening this issue at least until the notification suggested by @DonJayamanne is implemented.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
@microsoft microsoft unlocked this conversation Nov 14, 2020
@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 14, 2020
@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2021
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