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

New cells are created in the wrong Notebook document #120641

Closed
DonJayamanne opened this issue Apr 6, 2021 · 3 comments
Closed

New cells are created in the wrong Notebook document #120641

DonJayamanne opened this issue Apr 6, 2021 · 3 comments
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders notebook verified Verification succeeded
Milestone

Comments

@DonJayamanne
Copy link
Contributor

  • VS Code Version: latest Stable & insiders
  • OS Version: Mac

Steps to Reproduce:

  1. Install jupyter extension
  2. install kusto notebook extension
  3. Open jupyter notebook
  4. open a kusto notebook on the side
  5. set focus to jupyter notebook
  6. Click on add code/markdown cell in kusto notebook & watch how cells are created in the other notebook

wrongNb

@rebornix /cc

Does this issue occur when all extensions are disabled?: Yes/No

@vscodebot
Copy link

vscodebot bot commented Apr 6, 2021

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@rebornix rebornix added notebook bug Issue identified by VS Code Team member as probable bug labels Apr 6, 2021
@rebornix rebornix added this to the April 2021 milestone Apr 6, 2021
@rebornix
Copy link
Member

rebornix commented Apr 6, 2021

fixed via 3d6f300

digitarald pushed a commit that referenced this issue Apr 8, 2021
gjsjohnmurray pushed a commit to gjsjohnmurray/vscode that referenced this issue Apr 8, 2021
@rzhao271 rzhao271 added verified Verification succeeded and removed verified Verification succeeded labels Apr 28, 2021
@roblourens roblourens added the verified Verification succeeded label Apr 30, 2021
@github-actions github-actions bot locked and limited conversation to collaborators May 21, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders notebook verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

5 participants
@roblourens @rebornix @DonJayamanne @rzhao271 and others