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

It is no longer possible to debug scripts in 3.2 #11305

Closed
krassowski opened this issue Oct 18, 2021 · 1 comment · Fixed by #11311
Closed

It is no longer possible to debug scripts in 3.2 #11305

krassowski opened this issue Oct 18, 2021 · 1 comment · Fixed by #11311
Labels
bug pkg:debugger status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.

Comments

@krassowski
Copy link
Member

We may have missed testing the editor toolbar in #10727. As per the report in https://discourse.jupyter.org/t/jupyterlab-ide-customization/11271/5 it does not seem to be possible to debug standalone scripts anymore in 3.2 (which I confirmed locally). CC @3coins.

Expected result

debug-files-lab-3

Originally posted by @krassowski in #10727 (comment)

@3coins
Copy link
Contributor

3coins commented Oct 18, 2021

Looking into this.

@github-actions github-actions bot added the status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion. label Apr 18, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Apr 18, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug pkg:debugger status:resolved-locked Closed issues are locked after 30 days inactivity. Please open a new issue for related discussion.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants