# Juliaup appears to have corrupted julia language server information for vscode
**URL:** https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545
**Category:** VS Code
**Created:** [October 10, 2022, 11:41pm UTC](https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545 "2022-10-10T23:41:47Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@brianguenter](https://discourse.julialang.org/u/brianguenter)
#### Post date: [October 10, 2022, 11:41pm UTC](https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545/1 "2022-10-10T23:41:47Z")
I have been using vscode successfully with Julia on linux for years.
> **OS Version**
>
> Julia Version 1.8.2
> Commit 36034abf260 (2022-09-29 15:21 UTC)
> Platform Info:
> OS: Linux (x86\_64-linux-gnu)
> CPU: 128 × AMD EPYC 7702P 64-Core Processor
> WORD\_SIZE: 64
> LIBM: libopenlibm
> LLVM: libLLVM-13.0.1 (ORCJIT, znver2)
> Threads: 64 on 128 virtual cores
> Environment:
> JULIA\_NUM\_THREADS = 64
Today I ran juliaup to update to 1.8.2 and now the julia language server won’t start the repl from inside vscode (ctrl-shift-p Julia:start REPL). It opens the terminal pane for a few seconds then closes it without starting the REPL.
I assume this is because juliaup and the julia extension for vscode are not interacting well together. I uninstalled and reinstalled the julia language extension which didn’t fix the problem then uninstalled vscode and reinstalled it and the language extension which still didn’t fix the problem. There must be some cached state somewhere which is not being deleted.
I also tried manually entering the path to the julia executable. The only julia executable I can find is in the .julia/juliaup/julia-1.8.2+0.x64/bin folder but if I use that path the same problem occurs.
Anyone had this problem and figured out how to fix it?
---
### Author:  [@mkoculak](https://discourse.julialang.org/u/mkoculak)
#### Post date: [October 10, 2022, 11:52pm UTC](https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545/2 "2022-10-10T23:52:22Z")
Next to the terminal tab in VSCode there is also an output tab, where you can find logs from Julia, the language server, etc. Do you see anything there that might point to a problem?
---
### Author:  [@brianguenter](https://discourse.julialang.org/u/brianguenter)
#### Post date: [October 11, 2022, 12:13am UTC](https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545/3 "2022-10-11T00:13:38Z")
Here is the output from a fresh start of vscode with a single attempt to start the julia REPL.
```julia
[2022-10-10 18:27:10.274] [renderer1] [critical] Extension 'github.vscode-pull-request-github' wants API proposal 'badges' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
[2022-10-10 18:27:10.274] [renderer1] [critical] Extension 'github.vscode-pull-request-github' wants API proposal 'contribViewSize' but that proposal DOES NOT EXIST. Likely, the proposal has been finalized (check 'vscode.d.ts') or was abandoned.
[2022-10-10 18:27:14.299] [renderer1] [info] [eamodio.gitlens]: Command `gitlens.copyAutolinkUrl` appears multiple times in the `commands` section.
[2022-10-10 18:27:17.109] [renderer1] [error] [Extension Host] (node:66240) DeprecationWarning: uuidv4() is deprecated. Use v4() from the uuid module instead.
(Use `code --trace-deprecation ...` to show where the warning was created)
```
Running `ctrl-shift-P Julia:start REPL` doesn’t seem to cause any output.
---
### Author:  [@brianguenter](https://discourse.julialang.org/u/brianguenter)
#### Post date: [October 11, 2022, 1:51am UTC](https://discourse.julialang.org/t/juliaup-appears-to-have-corrupted-julia-language-server-information-for-vscode/88545/4 "2022-10-11T01:51:05Z")
i deleted .config/Code and .vscode and reinstalled julia and vscode from scratch. Now everything seems to work.