You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thank you for filing this issue, are you able to update ipykernel & debugpyto the latest version and see if this repros
Also, please update your version of VS Code, Jupyter and Python extensions to the latest versions (as you have some fairly old versions).
@DonJayamanne I upgraded to debugpy1.8.5 and ipykernel 6.29.5. Breakpoint still doesn't stop and I'm also seeing the same "Breakpoint in file that does not exist." response back to the extension.
Looking at the latest version of the code, I see that path.normalize is still getting called for sourcePath. From I understand in the code, path.normalize is the one flipping / to \ in the sourcePath. @adam-zlatniczki tried to fix this before as you can see in #11396
Applies To
What happened?
I'm facing is the same issue reported in #11396
with slightly different setup. My kernel is running in a linux container specifically https://hub.docker.com/layers/amazon/aws-glue-libs/glue_libs_4.0.0_image_01/images/sha256-bd642d06ee69c7eac710080091c5c76dfbf28005bb81541d475ab5846851368c?context=explore
ipykernel: 6.20.2
debugpy: 1.80
python: 3.10.2
VS Code Version
1.88.1
Jupyter Extension Version
v2023.11.1003402403
Jupyter logs
Coding Language and Runtime Version
No response
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
None
The text was updated successfully, but these errors were encountered: