Here is a quick guide on possible fixes you can try to fix existing errors before asking for help.

Existing Errors Codes

Jupyter process could not be spawned

Indicates that at the instant Jupyter is run, a problem occurs and Jupyter either never starts or crashes instantly.

  1. Check the provided Python executable to use is valid and that the path is set correctly if not using python.
  2. Check that Jupyter is installed in the provided Python environment. Depending on your Jupyter environment type, you will want to check Jupyter Lab or Jupyter Notebook in particular. You can do this using the command [python_executable] -m [notebook or jupyterlab] and see if Jupyter starts normally.

If both Python and the right Jupyter environment are installed, please open a ticket.

Jupyter process crashed

Indicates that Jupyter was started but then crashed before being fully ready to open .ipynb.

  1. Check that Jupyter is installed in the provided Python environment. Depending on your Jupyter environment type, you will want to check Jupyter Lab or Jupyter Notebook in particular. You can do this using the command [python_executable] -m [notebook or jupyterlab] and see if Jupyter starts normally.

If the right Jupyter environment is installed, please open a ticket.

Jupyter process exited

Very rare case that indicates Jupyter exited while starting, but did not encounter any error. This means the Jupyter process exited with a 0 exit code, meaning the program exited normally.

  1. Check for an exit() statement lost in your Jupyter configuration file if you have one.
  2. For more advanced users, you can enable Jupyter logging and try debugging the issue from the messages Jupyter gives you.

If none of those work, please open a ticket.

Jupyter Timeout

Indicates Jupyter was started and worked in the background for too long, thus it was considered that something was wrong.

  1. Check the value of your Jupyter starting timeout and try to increase it. This defines for how long to wait before considering Jupyter to be timing out. If set too low, this can prevent Jupyter from ever starting.

If increasing the Jupyter starting timeout to the maximum possible value does not work for you, please run Jupyter manually from the terminal, record how long it takes from the moment you enter the command to the moment Jupyter opens your browser. Then open a ticket where you indicate the measured time.

Opening a Ticket

If none of the fixes above work for you, you can request help using

  • GitHub issues Choose the issue template that seems appropriate to you. By default you’ll want to use Ask for help.
  • Discord server Join the Discord server and ask your questions in the home channel.

Your feedback and bug reports will help improve the plugin, thank you !