Vscode-jupyter: Can't run two notebooks at the same time with the same python environment (using native notebooks)

Created on 18 Aug 2020  路  6Comments  路  Source: microsoft/vscode-jupyter

Bug: Notebook Editor, Interactive Window, Editor cells

Steps to cause the bug to occur

  1. Open notebook 1 in new editor, select python env, run first cell - kernel starts and cell runs.
  2. Open notebook 2 in new editor, select python env, run first cell - kernel starts and cell runs.
  3. Go back to notebook 1, run any cell (even the first one) - nothing happens.
  4. go back to notebook 2, all cells run.

Actual behavior

cant run two notebooks together.

  • BOTH notebooks run together properly same way in the old editor

Expected behavior

both notebooks should be able to run cells at the same time

Your Jupyter and/or Python environment

_Please provide as much info as you readily know_

  • Jupyter server running: Local | Remote | N/A
  • Extension version: v2020.9.102277-dev
  • VS Code version: #.## 1.49.0-insider
  • Setting python.jediEnabled: true | false
  • Setting python.languageServer: Jedi | Microsoft | None
  • Python and/or Anaconda version: #.#.#
  • OS: Windows | Mac | Linux (distro):
  • Virtual environment: conda | venv | virtualenv | N/A | ...

Python Output

Screen Shot 2020-08-18 at 12 14 53 PM

Microsoft Data Science for VS Code Engineering Team: @rchiodo, @IanMatthewHuff, @DavidKutu, @DonJayamanne, @greazer, @joyceerhl

bug vscode-notebook

All 6 comments

@matrix303 thanks for filing this and for checking out the new notebook preview. I repro this behavior as well with our released version. Right now our support for the new preview notebooks is coming in very fast, so there will be a lot of improvements each version and lots of incoming changes. We'll look at the fix for this.

Np just letting you guys know!

We very much appreciate folks checking the preview work out and filing issues. It's going to take a bit to transition everything over cleanly, but the experience is going to be very good after it's all done.

I cannot reproduce this in version 2020.8.108011 of the extension and 1.49.0-insider. @matrix303 does this behavior persist for you?

Lets close for now, and will re-open if the issue persists.

Issue was solved in the later updates.

Was this page helpful?
0 / 5 - 0 ratings