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.

Sign up for GitHub

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

Jump to bottom

cell runs forever and can't interrupt if remote server is unavailable #10568

Closed
amunger opened this issue Jun 24, 2022 · 2 comments · Fixed by #11086
Closed

cell runs forever and can't interrupt if remote server is unavailable #10568

amunger opened this issue Jun 24, 2022 · 2 comments · Fixed by #11086
Assignees
@DonJayamanne
Labels
bug Issue identified by VS Code Team member as probable bug notebook-remote Applies to remote Jupyter Servers verified Verification succeeded
Milestone
August 2022

Comments

@amunger
Copy link
Contributor

amunger commented Jun 24, 2022

  1. Connect to a remote jupyter server
  2. Run a cell on a remote kernel
  3. Kill the server
  4. Run a cell on the same kernel

Result:
Cell stays in executing state indefinitely. Interrupt won't stop it.
@amunger amunger added bug Issue identified by VS Code Team member as probable bug notebook-remote Applies to remote Jupyter Servers labels Jun 24, 2022
@github-actions github-actions bot added the triage-needed Issue needs to be triaged label Jun 24, 2022
@greazer greazer added vscode-web and removed triage-needed Issue needs to be triaged labels Jun 27, 2022
@DonJayamanne
Copy link
Contributor

DonJayamanne commented Jun 27, 2022 •
edited
Loading

Isn't this a papercut,
I.e. the remote server is killed off midway while running a notebook.
If you close the notebook & reopen the notebook or reload VSCode then this isn't a problem.

@rchiodo rchiodo mentioned this issue Jul 27, 2022
Closed
@DonJayamanne DonJayamanne mentioned this issue Aug 8, 2022
Closed
25 tasks
@DonJayamanne DonJayamanne self-assigned this Aug 10, 2022
@DonJayamanne DonJayamanne mentioned this issue Aug 10, 2022
Merged
@DonJayamanne DonJayamanne added this to the August 2022 milestone Aug 22, 2022
@rzhao271
Copy link
Contributor

rzhao271 commented Aug 25, 2022 •
edited
Loading

This seems like a duplicate of #9828.
Marking this issue as verified to take it off the query, but see #9828 (comment).

@rzhao271 rzhao271 added the verified Verification succeeded label Aug 25, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Aug 26, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@DonJayamanne DonJayamanne

Labels
bug Issue identified by VS Code Team member as probable bug notebook-remote Applies to remote Jupyter Servers verified Verification succeeded
Projects
None yet
Milestone
August 2022
Development

Successfully merging a pull request may close this issue.

Handle situation when remote connection is lost microsoft/vscode-jupyter
4 participants
@DonJayamanne @amunger @rzhao271 @greazer