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

Up and down arrow keys stop working in cells #16372

Open
1 of 2 tasks
jgeorge0123 opened this issue Jan 11, 2025 · 0 comments
Open
1 of 2 tasks

Up and down arrow keys stop working in cells #16372

jgeorge0123 opened this issue Jan 11, 2025 · 0 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged

Comments

@jgeorge0123
Copy link

Applies To

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

What happened?

After running a notebook for some amount of time the up and down arrow keys stop working:

Result of "Developer: Toggle Keyboard Shortcuts Troubleshooting":

Normal key result:
2025-01-11 08:40:07.689 [info] [KeybindingService]: | Resolving [ArrowUp] 2025-01-11 08:40:07.689 [info] [KeybindingService]: \ From 22 keybinding entries, matched cursorUp, when: textInputFocus, source: built-in. 2025-01-11 08:40:07.689 [info] [KeybindingService]: / Received keydown event - modifiers: [], code: ArrowUp, keyCode: 38, key: ArrowUp 2025-01-11 08:40:07.689 [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: ArrowUp, keyCode: 16 ('UpArrow') 2025-01-11 08:40:07.689 [info] [KeybindingService]: | Resolving [ArrowUp] 2025-01-11 08:40:07.690 [info] [KeybindingService]: \ From 22 keybinding entries, matched cursorUp, when: textInputFocus, source: built-in. 2025-01-11 08:40:07.690 [info] [KeybindingService]: + Invoking command cursorUp.

Broken key result:
2025-01-11 08:45:01.654 [info] [KeybindingService]: / Soft dispatching keyboard event 2025-01-11 08:45:01.654 [info] [KeybindingService]: | Resolving [ArrowUp] 2025-01-11 08:45:01.654 [info] [KeybindingService]: \ From 22 keybinding entries, matched notebook.cell.nullAction, when: notebookOutputInputFocused, source: built-in. 2025-01-11 08:45:01.654 [info] [KeybindingService]: / Received keydown event - modifiers: [], code: ArrowUp, keyCode: 38, key: ArrowUp 2025-01-11 08:45:01.654 [info] [KeybindingService]: | Converted keydown event - modifiers: [], code: ArrowUp, keyCode: 16 ('UpArrow') 2025-01-11 08:45:01.655 [info] [KeybindingService]: | Resolving [ArrowUp] 2025-01-11 08:45:01.655 [info] [KeybindingService]: \ From 22 keybinding entries, matched notebook.cell.nullAction, when: notebookOutputInputFocused, source: built-in. 2025-01-11 08:45:01.655 [info] [KeybindingService]: + Invoking command notebook.cell.nullAction.

It appears that the notebook.cell.nullAction binding is matched when cursorUp should be matched. The same applies to the down arrow. Right and left are unaffected. I have seen this issue three times now in large Jupyter notebooks but I am not exactly sure how I am getting into this state.

VS Code Version

Version: 1.96.2 Commit: fabdb6a30b49f79a7aba0f2ad9df9b399473380f Date: 2024-12-19T10:22:47.216Z Electron: 32.2.6 ElectronBuildId: 10629634 Chromium: 128.0.6613.186 Node.js: 20.18.1 V8: 12.8.374.38-electron.0 OS: Darwin arm64 23.2.0

Jupyter Extension Version

2024.11.0

Jupyter logs

Visual Studio Code (1.96.2, undefined, desktop)
Jupyter Extension Version: 2024.11.0.
Python Extension Version: 2024.22.1.
Pylance Extension Version: 2024.12.1.
Platform: darwin (arm64).
==========================================================
Can't paste more since there is sensitive paths below. 
I noticed I did interrupt the cells for example:

19:23:40.418 [info] Interrupt kernel execution
19:23:40.418 [info] Interrupting kernel: python3124jvsc74a57bd08b4f51a7c16c84148fe04ebb932e710a11e865f663359a6faf15c5870f5147f0
19:23:40.418 [info] Interrupting kernel via SIGINT
19:23:40.792 [warn] Cell completed with errors (cancelled)

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

@jgeorge0123 jgeorge0123 added the bug Issue identified by VS Code Team member as probable bug label Jan 11, 2025
@vs-code-engineering vs-code-engineering bot added the triage-needed Issue needs to be triaged label Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Issue identified by VS Code Team member as probable bug triage-needed Issue needs to be triaged
Projects
None yet
Development

No branches or pull requests

2 participants