NameError: name '_VSCODE_getVariableInfo' is not defined

[yc1999]

I was debugging...

When I chose "view value in data viewer" for a variable at a checkpoint for the first time, it worked fine as normal.

Then I clicked F5, and the programme stopped at the same checkpoint.

But when I chose "view value in data viewer" for a variable again, it didn't work and the log was as follows

error 11:44:25.215: Error: Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name '_VSCODE_getVariableInfo' is not defined

    at o.handleErrorResponse (vscode-file://vscode-app/d:/vscode/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1041:45806)
    at vscode-file://vscode-app/d:/vscode/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1041:45245
warn 11:44:25.215: DataScience Error Error: Traceback (most recent call last):
  File "<string>", line 1, in <module>
NameError: name '_VSCODE_getVariableInfo' is not defined

    at o.handleErrorResponse (vscode-file://vscode-app/d:/vscode/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1041:45806)
    at vscode-file://vscode-app/d:/vscode/Microsoft%20VS%20Code/resources/app/out/vs/workbench/workbench.desktop.main.js:1041:45245

[yc1999]

What's more, when my programme first stoped at the checkpoint, the VARIABLES are as follows:

But when I clicked F5, and stopped at the checkpoint at scecond time, the VARIABLES are as follows:

So, as you can see , a lot of _VSCODE* variables disappeared, it's so wired...

[rchiodo]

Thanks for the issue. My guess is that the second breakpoint was a different module and we're not loading the evaluation objects correctly.

Can you describe the two breakpoints more? Or provide repro source? Thanks.

[yc1999]

emmm, the first breakpoint and the second breakpoint is the same. I clicked F5 to stop at the same checkpoint everytime.

[sanderdw]

I have the exact same problem.

[vincentvalton]

Same problem with either dataframe or tensors. Seems to have popped up during the last vscode update as it used to work fine before.

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "<string>", line 51, in _VSCODE_getVariableInfo
NameError: name '_VSCODE_json' is not defined. 
View Jupyter [log](command:jupyter.viewOutput) for further details.

[yc1999]

@rchiodo Hope you can help us address this issue 🙂 It used to work fine before, but in this week, this problem poped up.

[vincentvalton]

In the meantime as a workaround: I can confirm that regressing to vscode 1.67.2 fixes the issue.

https://code.visualstudio.com/updates/v1_67

[yc1999]

In the meantime as a workaround: I can confirm that regressing to vscode 1.67.2 fixes the issue.

https://code.visualstudio.com/updates/v1_67

oooooh, thank you.
😂Forgive me, I have one more question: If I download version 1.67.2, and install it to replace version 1.68. Will my resources in
the version 1.68 disapper in the version 1.67.2 ? (such as extensions, preferences...) @vincentvalton

[vincentvalton]

I have both versions installed, and all my preferences are there on both versions.

I had to downgrade the jupyter extension to an earlier version, but once that was done it all worked perfectly 👍 with the v1.67.2 (until the current version is updated and fixed)

[rchiodo]

Here's some code to repro the issue:

def foo():
    df.head() # Stick breakpoint here. First time view in data viewer works. Second time it doesn't.

import pandas as pd

df = pd.read_csv('data/test.csv')  

foo()
foo()
foo()

[rchiodo]

My guess would be this change:
505dc65

We used to load the script itself as a module. We don't do that because of needing to support web, but then since the code is only loaded once, we never reload for a new stack frame.

[rchiodo]

Test should be updated to make sure it causes more than one stack frame.

[rchiodo]

/verified

However the removal of the temporary functions doesn't seem to work: