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

[Endgame testing] ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior #6405

Closed
Tracked by #5607
meganrogge opened this issue Jun 29, 2021 · 2 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug notebook-run-by-line

Comments

@meganrogge
Copy link

testing microsoft/vscode#127362 , debugged with @DavidKutu

Expected behaviour

I expected debugging to work with ipykernel 5.5.5 installed

Actual behaviour

It did not and had some confusing behavior:

  • Jupyter: Debug appeared in the command palette, but only on window reload
  • I could set breakpoints, but they wouldn't get hit

To resolve this, I had to uninstall ipykernel and re-install the latest version with pip install ipykernel --pre

@meganrogge meganrogge added the bug Issue identified by VS Code Team member as probable bug label Jun 29, 2021
@meganrogge meganrogge changed the title ipykernel 6 required for debugging to work ipykernel 6 required for debugging to work - not informed when using lower version Jun 29, 2021
@meganrogge meganrogge changed the title ipykernel 6 required for debugging to work - not informed when using lower version ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior Jun 29, 2021
@DavidKutu DavidKutu changed the title ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior [Endgame testing] ipykernel 6 required for debugging to work - not informed when using lower version and strange behavior Jun 30, 2021
@DavidKutu
Copy link

Now that ipykernel 6 just released. I was thinking we could always expose the button and have it show a message if you don't have it and offer a button to do the installation for you.

@roblourens had another idea to make this feel more native, to remove the button altogether and have the session start silently when you open the notebook, there would be no extra steps to start debugging, just set a breakpoint and run cells.

@DavidKutu
Copy link

dupe of #7056

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 20, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug notebook-run-by-line
Projects
None yet
Development

No branches or pull requests

4 participants