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
Just as a background, where the confusion might come from: on #135 (marked as closed) they will link to --> microsoft/debugpy#1418 (marked as closed) they will link to --> microsoft/debugpy#1408 (also marked as closed)
I will inshallah try to create a new issue on debugpy, hoping that they do not mind and not forward me somewhere else.
The text was updated successfully, but these errors were encountered:
It's closed because the fix has been committed to the repo, but there hasn't been a debugpy release that includes the fix yet.
In the meantime, you can use the most recent bits from the repo by doing this in your launch.json (assuming that you cloned the repo into ~/git/debugpy):
Nice to hear that, the team did not forget about this issue. Thank you for the quick reply. Can you guess of a timeframe when the new release with this correction can be expected?
microsoft/vscode-python-debugger#135 was closed. However, the issue still remains, see:
Version: 1.85.2
Commit: 8b3775030ed1a69b13e4f4c628c612102e30a681
Date: 2024-01-18T06:40:19.222Z
Electron: 25.9.7
ElectronBuildId: 26354273
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: 11.4.183.29-electron.0
OS: Linux x64 5.14.21-150500.55.39-default
Additional
Also, please see: microsoft/vscode-python-debugger#183 (comment)
The text was updated successfully, but these errors were encountered: