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

Input Problems with Interactive Terminal #446

Closed
tsoud opened this issue Nov 9, 2020 · 18 comments
Closed

Input Problems with Interactive Terminal #446

tsoud opened this issue Nov 9, 2020 · 18 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug

Comments

@tsoud
Copy link

tsoud commented Nov 9, 2020

Issue Type: Bug

Typing directly into the Python interactive terminal is buggy. This seems to be an issue in the latest (October 2020) release since it began immediately after the update.

Expected result: You type something into the interactive terminal input cell and characters appear...

Actual result: You type into the interactive terminal and nothing happens. Usually, you can start typing after clicking the cursor a few times but many times the terminal input cell does not respond at all requiring a restart.

Extension version: 2020.10.332292344
VS Code version: Code 1.51.0 (fcac248b077b55bae4ba5bab613fd6e9156c2f0c, 2020-11-05T18:16:10.374Z)
OS version: Linux x64 5.4.0-52-generic

System Info
Item Value
CPUs Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 x 4000)
GPU Status 2d_canvas: enabled
flash_3d: enabled
flash_stage3d: enabled
flash_stage3d_baseline: enabled
gpu_compositing: enabled
multiple_raster_threads: enabled_on
oop_rasterization: disabled_off
opengl: enabled_on
protected_video_decode: unavailable_off
rasterization: disabled_software
skia_renderer: enabled_on
video_decode: unavailable_off
vulkan: disabled_off
webgl: enabled
webgl2: enabled
Load (avg) 0, 0, 0
Memory (System) 31.20GB (7.46GB free)
Process Argv . --no-sandbox
Screen Reader no
VM 0%
DESKTOP_SESSION cinnamon
XDG_CURRENT_DESKTOP X-Cinnamon
XDG_SESSION_DESKTOP cinnamon
XDG_SESSION_TYPE x11
@eioe
Copy link

eioe commented Nov 10, 2020

I experience the same since the last update. Interestingly, after restarting VSC it would work for 2-3 commands and then the terminal becomes unresponsive. That's very painful.

Info:
Extension version: v2020.10.332292344
VSC version: 1.51.0 (user setup)
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-05T18:18:23.642Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.18363 (Windows 10)

@jiaguo1000
Copy link

Same problem!

VSC:
Version: 1.51.0
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-05T18:14:40.758Z (5 days ago)
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 19.6.0

@DonJayamanne DonJayamanne transferred this issue from microsoft/vscode-python Nov 11, 2020
@ihnorton
Copy link

ihnorton commented Nov 11, 2020

Click-dragging the "Python Interactive" tab and moving it to a new split position (eg side by side or the reverse) seems to fix the problem temporarily :/

Version: 1.51.1
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-11T01:11:34.018Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Darwin x64 18.7.0

@rboyes
Copy link

rboyes commented Nov 12, 2020

Same issue here

Version: 1.51.1 (user setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.17763

@IanMatthewHuff
Copy link
Member

Hey everyone. Just wanted to comment to thank folks for reporting this issue. I'm able to repro this as well, and I'm looking into it. Not fully sure on the cause yet as the repro is (at least for me) very sporadic for when it happens.

@tsoud
Copy link
Author

tsoud commented Nov 12, 2020

@IanMatthewHuff thanks for taking this on! In my case it's sporadic but frequent, and especially noticeable when switching back and forth between the editor and interactive window.

Additional note: I just updated from 1.51.0 to 1.51.1 (e5a624b788d92b8d34d1392e4c4d9789406efe8f) and the issue persists.

@tsoud
Copy link
Author

tsoud commented Nov 14, 2020

Another update:
When the prompt in the interactive window won't accept input, I noticed that using Ctrl '+' followed by Ctrl '-' (i.e. zooming in and zooming back out) on my Linux system fixes it temporarily.
This is the same workaround I use when the text in my VSCode terminal window disappears every now and then.

@GusHebblewhite
Copy link

GusHebblewhite commented Nov 16, 2020

+1 for this issue

Version: 1.51.1 (user setup)
Commit: e5a624b788d92b8d34d1392e4c4d9789406efe8f
Date: 2020-11-10T23:34:32.027Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Windows_NT x64 10.0.19041

@azz147
Copy link

azz147 commented Nov 16, 2020

Press ctrl+B can temporarily fix this on windows(and also on wsl2), but will happen again very soon,

@janosh
Copy link
Contributor

janosh commented Nov 16, 2020

The suggestions by @ihnorton to drag the interactive window to a new editor group and by @tsoud zooming in and out (even faster) are both working as temporary fixes. Thanks for that!

@greazer
Copy link
Member

greazer commented Nov 17, 2020

Lots of dupes being entered for this issue, so marking as high-priority.

@rchiodo
Copy link
Contributor

rchiodo commented Nov 17, 2020

If I click back and forth between the python editor and the interactive window a bunch, it seems to repro every time. Might be related to our focus tracking.

@rchiodo
Copy link
Contributor

rchiodo commented Nov 17, 2020

Root cause looks to be that the body of the interactive window has focus when the monaco editor thinks it does. So when we tell the monaco editor to take focus it doesn't.

Not sure yet what is stealing focus away for the body yet.

@rchiodo
Copy link
Contributor

rchiodo commented Nov 17, 2020

Seems like the VS code webview code is stealing focus. The activate message we send can interfere with this focus. IF we don't use this activate the IW won't lock up (although then it won't get focus unless you click on it).

@IanMatthewHuff
Copy link
Member

Validated based on our bug bash testing.

@bk8190
Copy link

bk8190 commented Nov 20, 2020

azz147 solution of pressing ctrl-B works for me - it temporarily fixes the problem on Windows and is easier than moving the window to a new pane

@thanosgatos
Copy link

I am experiencing the same thing. I was about to create a new issue, but I saw all the late ones have been closed as duplicates. This is still an issue that occurs every few minutes. It has actually been getting worse. It's becoming a blocker. Is there still no solution to this?

@rchiodo
Copy link
Contributor

rchiodo commented Dec 10, 2020

I am experiencing the same thing. I was about to create a new issue, but I saw all the late ones have been closed as duplicates. This is still an issue that occurs every few minutes. It has actually been getting worse. It's becoming a blocker. Is there still no solution to this?

@thanosgatos What is your extension version? This should have been fixed already.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 6, 2021
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
Projects
None yet
Development

No branches or pull requests