-
Notifications
You must be signed in to change notification settings - Fork 300
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
Stop automatically creating jupyter notebooks when using interactive window #8984
Comments
@rob-mccutcheon Thanks for the report here, this isn't something that should be happening. Could you please in this scenario where the files are being created pull the logs from the Jupyter section of the VS Code output window? That would have our diagnostic logging that we can use to investigate this. Also the version of VS Code and the Jupyter extension that you are using would be helpful. |
Thanks @IanMatthewHuff It is VS Code 1.64.2 and Jupyter v2022.1.1001821375 On further exploration this seems to be only occurring on remote hosts, I am using Remote -SSH v0.70.0 The contents of the output window is
|
Sorry! Here is the jupyter log:
|
Thanks for the more detailed log. At the start there are some issues with starting up the jupyter server, but I don't think that's the root issue here. To me it looks like this bit here is the core issue:
This is our call to the Jupyter notebook API to clean up the notebook file that we created. Is there maybe some type of symlink situation here that is happening? This error is happening in the Jupyter server itself, we are just calling the Jupyter API to delete the temp file. Sounds possibly related to home and root being on different directories? One thing to note, at the start we first attempt to start up ipython directly with ZMQ, this fails and we fallback to using the Jupyter server. The error that you have there |
Thanks @IanMatthewHuff I think the home and root being on different directories may be tricky to fix as issue persists whether accessing the code directly or via a symlink on the home directory I have tried with ensuring that .cshrc loads more recent gcc versions (have tried 10.2.0 and 7.5.0) but getting the same error:
|
@rob-mccutcheon I've looked into this a bit more, and for now I'm going to mark this as an upstream issue. For a Jupyter connection we rely on the jupyterlab services to perform file deletion. Right now this same issue is an open issue on Jupyter. We might still be able to help with this from our side, but the fix would probably have to happen in the Jupyter source base and I don't believe that would be in the near future. |
@rob-mccutcheon I believe this has been fixed in the latest pre-release version of the Jupyter extension. Possibly a duplicate of #6510 |
Thanks @DonJayamanne - the ipynb notebooks don't appear to be created. There is still a pycache folder created, I dont know if that is also unwanted behaviour? |
not sure about that, if you believe it's created by this extension, please file an issue. its most likely created by the python runtime for your modules. closing as a duplicate of #6510 |
I encountered the same problem when I use vs code in a Google drive directory, while running a code in a normal local path will not have this problem. |
I typically use the python interactive window to explore scripts. Since one of the updates, however, this now automatically generate a .ipynb notebook in whichever directory I am in, cluttering the file system.
Is there a way to use the interactive window without it automatically creating a .ipynb file?
The text was updated successfully, but these errors were encountered: