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

Kernel selection fails for first several seconds while it's launching the kernel in the background #5143

Open
MSeal opened this issue Jun 3, 2020 · 1 comment

Comments

@MSeal
Copy link
Member

MSeal commented Jun 3, 2020

Application or Package Used
State which application or package this affects. For example: nteract desktop, nteract web, nteract on jupyter, etc.

nteract on jupyter

Describe the bug
A clear and concise description of what the bug is.

When loading a notebook for the first time it states the notebook is disconnected. When you run a cell you can get this message and a halted execution:

Execute failed
There is no connected kernel for this content.

if the kernel doesn't start fast enough. A second after this message the kernel in the bottom left says it's now idle and rerunning the cell succeeds.

To Reproduce
Steps to reproduce the behavior:

  1. Launch nteract
  2. Load a python3 notebook
  3. Run the first cell
  4. See error message
  5. See kernel idle message in bottom left right after

Expected behavior
A clear and concise description of what you expected to happen.

First executions should await the kernel being ready after firing a launch request, rather than trying immediately and failing while the kernel is launching.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

  • OS: Ubuntu 20.04
  • Browser Chrome
  • Version current master branch

Additional context
Add any other context about the problem here.

@stale
Copy link

stale bot commented Jan 9, 2022

This issue hasn't had any activity on it in the last 90 days. Unfortunately we don't get around to dealing with every issue that is opened. Instead of leaving issues open we're seeking to be transparent by closing issues that aren't being prioritized. If no other activity happens on this issue in one week, it will be closed.
It's more than likely that just by me posting about this, the maintainers will take a closer look at these long forgotten issues to help evaluate what to do next.
If you would like to see this issue get prioritized over others, there are multiple avenues 🗓:

  • Ask how you can help with this issue 👩🏿‍💻👨🏻‍💻
  • Help solve other issues the team is currently working on 👨🏾‍💻👩🏼‍💻
  • Donate to nteract so we can support developers to work on these features and bugs more regularly 💰🕐

Thank you!

@stale stale bot added the stale workflow: stale issue label Jan 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants