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

Sometimes Interactive Window doesn't display the input code. #173590

Closed
1 of 2 tasks
forestGoroli opened this issue Feb 4, 2023 · 16 comments
Closed
1 of 2 tasks

Sometimes Interactive Window doesn't display the input code. #173590

forestGoroli opened this issue Feb 4, 2023 · 16 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release insiders-released Patch has been released in VS Code Insiders notebook-layout verified Verification succeeded

Comments

@forestGoroli
Copy link

Applies To

  • Notebooks (.ipynb files)
  • Interactive Window and/or Cell Scripts (.py files with #%% markers)

What happened?

Simplified reproduction method for my own use.

  1. Prepare many cells (more than 5?) and Run from "Jupyter: Run All Cells."
  2. Run the code from the interactive cell a few times (around 5).
  3. Sometimes window doesn't display the input code. (Output is still showing.)

The attached image is an example of this bug.

  1. I prepared the code consisting of 9 cells (1 for markdown, 8 for dummy code).
  2. Then I typed "print('aa')" into the interactive window 5 times.
  3. 3 / 5 of the input cells don't display my code.
    2023-02-04 161940
    2023-02-04 162048

I've also used the interactive window for debugging the short code, so not displaying my input code is a little unusable.

VS Code Version

Version: 1.75.0 (user setup) Commit: e2816fe Date: 2023-02-01T15:23:45.584Z Electron: 19.1.9 Chromium: 102.0.5005.194 Node.js: 16.14.2 V8: 10.2.154.23-electron.0 OS: Windows_NT x64 10.0.19045 Sandboxed: No

Jupyter Extension Version

v2023.1.2000312134

Jupyter logs

No response

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?

Local

@forestGoroli forestGoroli added the bug Issue identified by VS Code Team member as probable bug label Feb 4, 2023
@DonJayamanne DonJayamanne assigned rebornix and amunger and unassigned DonJayamanne Feb 4, 2023
@TheProjectsGuy
Copy link

I have the same issue. I think the earlier VSCode release did not have this problem.

Jupyter extension version: v2023.1.2000312134
VSCode version

1.75.0
e2816fe719a4026ffa1ee0189dc89bdfdbafb164
x64

@forestGoroli
Copy link
Author

Thank you very much!
I faced this problem after February, so as you said, I think this problem is only for the latest version (v2023.1.2000312134).

@gitgud5000
Copy link

gitgud5000 commented Feb 5, 2023

Experiencing the same issue as well.

Jupyter version: v2023.1.2000312134
VSCode: 1.75.0 x64

@TheProjectsGuy
Copy link

I tried installing version v2022.11.1003412109 with the latest VSCode release.

1.75.0
e2816fe719a4026ffa1ee0189dc89bdfdbafb164
x64

It gives the same problem. Could this be a VSCode issue?
There seems to be an issue about this already: #173300
image

@ZupoLlask
Copy link

This issue is important... I need to be collapsing and expanding cells all the time, to be able to see the code.

@sergeykorablin
Copy link

have the same problem

Version: 1.75.0
Commit: e2816fe
Date: 2023-02-01T15:29:17.766Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Linux x64 6.1.8-200.fc37.x86_64
Sandboxed: No

@PlanoCode
Copy link

I see this problem too but it appears to only fail to render the code cells when I have both the code and output expanded. If I collapse the output then I can scroll away from a code cell (out of view) then back to view without an issue. If both the code and output are expanded, scrolling away and back results in the code cell not rendering until it is collapsed and expanded again.

Jupyter Plugin: v2023.2.1000360234 (also tested with the non-pre-release)
Version: 1.75.0 (user setup)
Commit: e2816fe
Date: 2023-02-01T15:23:45.584Z
Electron: 19.1.9
Chromium: 102.0.5005.194
Node.js: 16.14.2
V8: 10.2.154.23-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

Can anyone help open Developer Tools (F1 -> Toggle Developer Tools) and share errors/logs in the dev tools with us to help troubleshoot?

@PlanoCode
Copy link

PlanoCode commented Feb 6, 2023

@rebornix Looking at the console of the dev tools, all scrolling produces lots of the attached errors. It happens scrolling in either direction, it happens if only collapsed code/output sections are visible, it happens with expanded code/output sections. If you scroll so that an expanded code and output cell are out of view, then scroll back the code cell does not appear. The height of the cell is unchanged but all of it's contents are missing including the lighter grey box where the text/code would usually appear.

vscode-app-1675659298181.txt

EDIT:
Some more curious details, if I expand all cells I continue to get the same error but only when the top of a new code cell comes into view. So when you scroll down the page as soon as a new cell comes into view you receive the error but scrolling up you can see the bottom of the cell without a new error occurring until you reach the top of the cell and it is completely in view.

Also with all cells expanded I do not have the issue with any of the cells disappearing and I do not need to collapse and expand a code or output cell to make the code cell's contents visible.

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

@PlanoCode thanks for providing the logs and reproduce steps! Your reproduce steps made me wonder if anything goes wrong with the collapse cell initial rendering, it would be great if you can share all logs you saw in Developer Tools as it seems that the log you shared is not the one leading to the bug.

3 similar comments
@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

@PlanoCode thanks for providing the logs and reproduce steps! Your reproduce steps made me wonder if anything goes wrong with the collapse cell initial rendering, it would be great if you can share all logs you saw in Developer Tools as it seems that the log you shared is not the one leading to the bug.

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

@PlanoCode thanks for providing the logs and reproduce steps! Your reproduce steps made me wonder if anything goes wrong with the collapse cell initial rendering, it would be great if you can share all logs you saw in Developer Tools as it seems that the log you shared is not the one leading to the bug.

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

@PlanoCode thanks for providing the logs and reproduce steps! Your reproduce steps made me wonder if anything goes wrong with the collapse cell initial rendering, it would be great if you can share all logs you saw in Developer Tools as it seems that the log you shared is not the one leading to the bug.

@PlanoCode
Copy link

@rebornix I am continuing to use the notebook and that that appears to be the only error I receive:

Screenshot 2023-02-05 233816

Screenshot 2023-02-05 234132

Collapsing a code cell does not appear to trigger any new messages except if doing so causes an code cell to come into view (does not cause an error if a MD or Output cell comes into view.) In my test even if I collapse all the code cells and expand one toward the top, once I collapse it I will receive that message on the console for every collapsed code cell that comes into view (ex 8 messages if there are 8 code cells, 1 output and 1 markdown (all collapsed))

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

@PlanoCode I can now reproduce the issue with the steps you provided, will fix it in Insiders tomorrow and have it fixed in VS Code recovery build. Thank you for the patience and help with the troubleshooting.

@rebornix
Copy link
Member

rebornix commented Feb 6, 2023

The fix will be available in tomorrow's Insiders and also the next Stable recovery build (in a couple of days).

@VSCodeTriageBot VSCodeTriageBot added insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Feb 7, 2023
@rebornix rebornix added the candidate Issue identified as probable candidate for fixing in the next release label Feb 7, 2023
@roblourens roblourens added the verified Verification succeeded label Feb 7, 2023
@github-actions github-actions bot locked and limited conversation to collaborators Mar 23, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release insiders-released Patch has been released in VS Code Insiders notebook-layout verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

10 participants