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

Unable to open the ipynb file once an interactive window is saved #208016

Closed
DonJayamanne opened this issue Mar 18, 2024 · 1 comment · Fixed by #209461
Closed

Unable to open the ipynb file once an interactive window is saved #208016

DonJayamanne opened this issue Mar 18, 2024 · 1 comment · Fixed by #209461
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug insiders-released Patch has been released in VS Code Insiders verified Verification succeeded
Milestone

Comments

@DonJayamanne
Copy link
Contributor

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

  • VS Code Version: Insiders
  • OS Version: N/A

Steps to Reproduce:

  1. Run cells in Python file to start an IW
  2. Press ctrl+s to save the IW as an ipynb file
  3. Provide a name
  4. The created ipynb file cannot be opened.
@DonJayamanne DonJayamanne reopened this Mar 18, 2024
@DonJayamanne DonJayamanne added the bug Issue identified by VS Code Team member as probable bug label Mar 18, 2024
@DonJayamanne
Copy link
Contributor Author

Screenshot 2024-03-19 at 01 49 15

@vscodenpa vscodenpa added unreleased Patch has not yet been released in VS Code Insiders insiders-released Patch has been released in VS Code Insiders and removed unreleased Patch has not yet been released in VS Code Insiders labels Apr 3, 2024
@rzhao271 rzhao271 added this to the April 2024 milestone Apr 24, 2024
@eleanorjboyd eleanorjboyd added the verified Verification succeeded label Apr 24, 2024
@microsoft microsoft locked and limited conversation to collaborators Jun 10, 2024
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 verified Verification succeeded
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants
@DonJayamanne @amunger @rzhao271 @eleanorjboyd @vscodenpa and others