microsoft / vscode-jupyter

VS Code Jupyter extension
https://marketplace.visualstudio.com/items?itemName=ms-toolsai.jupyter
MIT License
1.3k stars 293 forks source link

Can't run two notebooks at the same time with the same python environment (using native notebooks) #655

Closed matrix303 closed 3 years ago

matrix303 commented 4 years ago

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.

Your Jupyter and/or Python environment

Please provide as much info as you readily know

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

IanMatthewHuff commented 4 years ago

@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.

matrix303 commented 4 years ago

Np just letting you guys know!

IanMatthewHuff commented 4 years ago

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.

joyceerhl commented 4 years ago

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

DonJayamanne commented 4 years ago

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

matrix303 commented 4 years ago

Issue was solved in the later updates.