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

Python Debugger not showing NumPy array values after update - NOT resolved #1505

Open
jav-ed opened this issue Jan 30, 2024 · 2 comments
Open

Comments

@jav-ed
Copy link

jav-ed commented Jan 30, 2024

microsoft/vscode-python-debugger#135 was closed. However, the issue still remains, see:

0
1

  • VSCode Version:
    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)

Sorry, my bad.

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.

@int19h
Copy link
Contributor

int19h commented Jan 30, 2024

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):

"debugAdapterPath": "${userHome}/git/debugpy/src/debugpy/adapter"

(you'll get an error squiggle from the JSON schema validator because it doesn't know about this property, but it should still work)

@jav-ed
Copy link
Author

jav-ed commented Jan 31, 2024

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants