-
Notifications
You must be signed in to change notification settings - Fork 292
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
Can not reload .env when ZMQ not working #9774
Comments
I think this is related to #9480, although that issue is closed. |
Thanks for the issue. This is a function of how we start kernels on your machine. We're not pulling in the There's two things you can do:
or
That other process is only started once. The bug here is that the On my machine that process has a command line like so:
with the If you kill the jupyter_daemon process, it should force us to recreate it and pick up your |
The only way I have found to solve this issue (Apple M1) is to delete the kernelspec for vscode everytime I change the
|
Yeah for Mac M1, there's no workaround for ZMQ support. ZMQ needs to generate new node binaries for M1. So the only workaround is to stop the jupyter server (and it sounds like kill the kernel.json files - oh yes, we write the ENV to them. That should be how we could fix this.) |
Yes this is correct. Insepecting the kernel.json does show the environment variables as being written there. Do you know of a way to run an extra start up command prior to launching vscode or the jupyter server? ie the find -delete from above |
Maybe. The only thing that comes to mind is to modify your jupyter source code on disk. The py files that get launched when we run 'jupyter notebook'. Otherwise all startup code is run after the kernel has already started. Theoretically you could run your own code there that imported the Our setting for running code when the kernel starts is:
|
Should be fixed with #10843 |
Applies To
What happened?
The env variables in the .env file will be loaded after installing the vscode-jupyter extension and first running a notebook. However, when I change the variable values in .env, those values are never updated in future runs even after 1. restarting the kernel 2. reloading the window 3. restarting the vscode.
The only walkaround so far is reinstalling vscode-jupyter extension everytime, which is clearly not a feasible solution.
VS Code Version
1.66.2
Jupyter Extension Version
v2022.3.1000901801
Jupyter logs
Coding Language and Runtime Version
Python 3.9
Language Extension Version (if applicable)
No response
Anaconda Version (if applicable)
No response
Running Jupyter locally or remotely?
Remote
The text was updated successfully, but these errors were encountered: