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

No indication that kernel is starting when it's starting... #7134

Closed
greazer opened this issue Aug 14, 2021 · 4 comments
Closed

No indication that kernel is starting when it's starting... #7134

greazer opened this issue Aug 14, 2021 · 4 comments
Labels
bug Issue identified by VS Code Team member as probable bug notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) papercut 🩸 Something affecting the productivity of the team verified Verification succeeded
Milestone
January 2022

Comments

@greazer
Copy link
Member

greazer commented Aug 14, 2021 •
edited
Loading

Version: 1.60.0-insider (user setup)
Commit: 58454f7bec838f79fe2422ab5914419147d82e40
Date: 2021-08-13T05:15:29.421Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

v2021.8.2027072902

  1. Open a notebook
  2. Select a kernel other than whatever it defaulted to, using the kernel selection button at the top right.
  3. Run the first cell

I'm seeing no notification anywhere that a kernel is starting. It does start eventually and work though. Looks like step 2 is most important to be done. At least I DO see the kernel starting message if the notebook didn't have a good default kernel to start and I just run the first cell and choose the kernel from that initial popup.
@greazer greazer added bug Issue identified by VS Code Team member as probable bug regression labels Aug 14, 2021
@greazer greazer added notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) papercut 🩸 Something affecting the productivity of the team and removed needs-triage labels Aug 14, 2021
@greazer greazer added this to the September 2021 milestone Aug 20, 2021
@greazer greazer modified the milestones: September 2021, October 2021 Sep 20, 2021
@greazer greazer modified the milestones: October 2021, November 2021 Oct 25, 2021
@greazer
Copy link
Member Author

greazer commented Oct 25, 2021

Easy workaround - Trust it's starting and/or Open the Jupyter output tab

@DonJayamanne
Copy link
Contributor

@greazer how is this a regression?

@DonJayamanne DonJayamanne mentioned this issue Oct 26, 2021
Closed
@rchiodo rchiodo modified the milestones: November 2021, January 2022 Dec 6, 2021
@DonJayamanne
Copy link
Contributor

Should be fixed now, closing so this gets validated

@IanMatthewHuff IanMatthewHuff added the verified Verification succeeded label Jan 28, 2022
@IanMatthewHuff
Copy link
Member

We get this message now right from the start of execution. Verified.
image

@DonJayamanne DonJayamanne mentioned this issue Feb 21, 2022
Closed
1 task
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jan 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
bug Issue identified by VS Code Team member as probable bug notebook-execution Kernels issues (start/restart/switch/execution, install ipykernel) papercut 🩸 Something affecting the productivity of the team verified Verification succeeded
Projects
None yet
Milestone
January 2022
Development

No branches or pull requests
4 participants
@IanMatthewHuff @DonJayamanne @greazer @rchiodo