Random files appearing in my trash bin everytime I open a Jupyter notebook
See original GitHub issueEnvironment data
- VS Code version: 1.68.0
- Jupyter Extension version (available under the Extensions sidebar): v2022.5.1001601848
- Python Extension version (available under the Extensions sidebar): v2022.8.0
- OS (Windows | Mac | Linux distro) and version: MAC OS MONTEREY 12.4
- Python and/or Anaconda version: mamba 0.22.1 py39hde45b87_0 conda-forge, conda 4.12.0 py39h2804cbe_0 conda-forge
- Type of virtual environment used (N/A | venv | virtualenv | conda | …): conda
- Jupyter server running: Local | Remote | N/A : Local and Remote
Expected behaviour
Previously when I was running Jupiter notebooks, they were working fine.
Actual behaviour
When I open Jupyter notebooks in vscode now, these files appear in my trash bin automatically. Each one is 72 bytes, the file names are in the following format, "name of file"-jvsc-1ddefa11-e9b6-4e53-af4e-c472c2608261e3c71dba-91c1-44d1-af5e-b96ffff8817d.ipynb
and contain the following code { "cells": [], "metadata": {}, "nbformat": 4, "nbformat_minor": 5 }
They always produce the same file just with a different name. I am worried that this is going to destroy my hard from the constant read and writes. I am running the files from an external APFS SSD drive if that makes a difference.
Steps to reproduce:
[NOTE: Self-contained, minimal reproducing code samples are extremely helpful and will expedite addressing your issue]
-
Open a jupyter notebook in vscode using mambaforge
-
Save the file and reopen it.
-
Open the trash bin and you will see the file I am talking about.
Logs
Output for Jupyter
in the Output
panel (View
→Output
, change the drop-down the upper-right of the Output
panel to Jupyter
)
XXX
Issue Analytics
- State:
- Created a year ago
- Reactions:1
- Comments:10 (6 by maintainers)
Zeromq is native to Mac arm according to this https://formulae.brew.sh/formula/zeromq#default Is there anyway to enable it? @DonJayamanne @amunger
This will get fixed when #5206 is resolved. Hence closing this as a duplicate of #5206