# Can't access a live workspace for Julia when using integrated notebooks in VS Code

**URL:** <https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008>\
**Category:** VS Code\
**Created:** [May 31, 2022, 6:14pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008 "2022-05-31T18:14:56Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![lewis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lewis/32/5217_2.png) [@lewis](https://discourse.julialang.org/u/lewis)\
**Post date:** [May 31, 2022, 6:14pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/1 "2022-05-31T18:14:56Z")

</div>

Well, the title kind of says it. According to the docs for Vs Code Julia support it should be possible to see the Julia workspace while using Notebooks.

I can’t get this to work and I see no way to do so. I am using the integrated VS Code support for notebooks, not Python Jupyter. I am using an IJulia kernel and not the kernel provided by the language server.

The Julia language server’s jupyter kernel constantly hung or crashed, so I stopped using it.

I changed my config for the internal VS Code jupyter notebook, so I will try to LS’s kernel again because I believe that is the only kernel that provides workspace support.

“Wish me luck…!”

---

<div class="post-metadata">

**Author:** ![lewis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lewis/32/5217_2.png) [@lewis](https://discourse.julialang.org/u/lewis)\
**Post date:** [May 31, 2022, 6:50pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/2 "2022-05-31T18:50:09Z")

</div>

Great News!

1. Obviously, one must use the language server kernel for a live workspace on the notebook.
2. It works.
3. The settings changes I made in VS Code end the crashes and timeouts for the notebook in VS Code when using either external kernels (IJulia) or the language server kernel.

I am not sure _which_ of these settings made things work, but one or more of them did it:

```julia
"jupyter.experiments.enabled": false,
"jupyter.jupyterInterruptTimeout": 50000,
"jupyter.jupyterLaunchTimeout": 20000,
"jupyter.jupyterServerType": "local",
"jupyter.useDefaultConfigForJupyter": false,

```

---

<div class="post-metadata">

**Author:** ![Jaepil\_Lee](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jaepil_lee/32/9146_2.png) [@Jaepil\_Lee](https://discourse.julialang.org/u/Jaepil_Lee)\
**Post date:** [August 22, 2022, 1:42am UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/4 "2022-08-22T01:42:20Z")

</div>

Hi lewis,

Even after I applied the settings you posted, I am still getting the following crashes. Could you think of other solutions?

```julia
info 21:39:48.592: Cancel pending cells
info 21:39:48.592: Interrupt kernel execution
info 21:39:48.592: Interrupting kernel: julia-1.7
info 21:39:48.592: Interrupting kernel with a shell message
warn 21:40:38.596: Error during interrupt: Error: Kernel interrupt failed. Jupyter server is hung. Please reload VS Code.

```

---

<div class="post-metadata">

**Author:** ![lewis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lewis/32/5217_2.png) [@lewis](https://discourse.julialang.org/u/lewis)\
**Post date:** [August 22, 2022, 3:27pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/5 "2022-08-22T15:27:39Z")

</div>

Are you on Julia for Mac M1/M2? At the end of the day, I had to go back to intel MacOS with Julia 1.7 and then the crashes and problems stopped.

Julia 1.8 just shipped with improved support for Apple Silicon. I am giving it a try today.

---

<div class="post-metadata">

**Author:** ![Jaepil\_Lee](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/jaepil_lee/32/9146_2.png) [@Jaepil\_Lee](https://discourse.julialang.org/u/Jaepil_Lee)\
**Post date:** [August 22, 2022, 6:50pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/6 "2022-08-22T18:50:18Z")

</div>

I am using Julia for Windows with an Intel CPU. I also raised this issue on Github for VS Code, and it looks like this problem is coming from the Julia kernel itself:

[https://github.com/microsoft/vscode-jupyter/issues/10328](https://github.com/microsoft/vscode-jupyter/issues/10328)

---

<div class="post-metadata">

**Author:** ![lewis](https://sea2.discourse-cdn.com/julialang/user_avatar/discourse.julialang.org/lewis/32/5217_2.png) [@lewis](https://discourse.julialang.org/u/lewis)\
**Post date:** [August 22, 2022, 10:26pm UTC](https://discourse.julialang.org/t/cant-access-a-live-workspace-for-julia-when-using-integrated-notebooks-in-vs-code/82008/7 "2022-08-22T22:26:49Z")

</div>

Yes, I’ve seen that issue and it’s not what I mentioned. You should report at the GitHub repository for the Julia VS Code extension. Good luck.

- Lewis