Vscode-julia 1.2.4 fails with alt + enter execution (ctrl+enter works)

Tooling VS Code
1

update: tried the same setup with standard Julia 1.6.1 (as opposed to custom compile) and everything checks out. There should be something wrong with my Julia compile.

On vscode 1.57.0 with julia 1.5.3 the ALT+ENTER execution fails with the error below. Anyone else with similar experience? Can someone point me to the direction where I could start digging/unravelling the error message below?
best wishes: steven

Version: 1.57.0
Commit: 605d200353dbca6137c470fe16af16ffe56702c2
Date: 2021-06-14T01:49:32.567Z
Electron: 12.0.9
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Linux x64 5.4.0-72-generic

[2021-06-15 13:26:23.072] [exthost] [error] Error: Connection to server got closed. Server will not be restarted.
	at _.handleConnectionClosed (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:67714)
	at _.handleConnectionClosed (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:7:51522)
	at t (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:65493)
	at invoke (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:122416)
	at o.fire (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:123177)
	at Y (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:7:165779)
	at invoke (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:122416)
	at o.fire (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:1:123177)
	at m.fireClose (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:7:155852)
	at Socket.<anonymous> (/home/steven/.vscode-oss/extensions/julialang.language-julia-1.2.4/dist/extension.js:7:157432)
	at Socket.emit (events.js:327:22)
	at Pipe.<anonymous> (net.js:673:12) language-julia.executeCodeBlockOrSelectionAndMove

julia> versioninfo()
Julia Version 1.5.3
Commit 788b2c77c1 (2020-11-09 13:37 UTC)
Platform Info:
  OS: Linux (x86_64-linux-gnu)
  CPU: Intel(R) Core(TM) i7-8665U CPU @ 1.90GHz
  WORD_SIZE: 64
  LIBM: libimf
  LLVM: libLLVM-9.0.1 (ORCJIT, skylake)
Environment:
  JULIA_DEPOT_PATH = /home/steven/.julia:/usr/local/share/julia-depot
  JULIA_EDITOR = code
  JULIA_HDF5_PATH = /usr/local/
  JULIA_LOAD_PATH = @:@v#.#:@stdlib:/home/steven/.julia:/usr/local/share/julia-depot/environments/globalenv
  JULIA_MPIEXEC = srun
  JULIA_MPI_ABI = OpenMPI
  JULIA_MPI_BINARY = system
  JULIA_MPI_LIBRARY = libmpi
  JULIA_MPI_PATH = /usr/local
  JULIA_NUM_THREADS = 
  JULIA_PROJECT = /opt/projects/analytics
2

I also keep having problems with ALT+ENTER on and off. Sometimes highlighting the code block helps , sometimes not. Sometimes it recognises the code blocks sometimes it doesn’t. No idea how to reproduce.

3

I don’t have such problems, but I do have a huge delay (tens of seconds) on Windows after starting a fresh vscode and Alt+Enter first line of code - and before “executing” symbol starts to show next to the line. Sometimes it is even longer, if REPL starts with Precompiling VSCodeServer message (I suppose due to vscode or Julia plugin updates).

4

there is also a freeze during package indexing, but then at least I see something is happening.

5

yes, this is something to do with Julia infrastructure. I gutted/hacked a previous vscode-julia in December, 2020 with success; but 1.4.2 has gone a long way since in features and footprint. For good experience you need fast computer/ good setup and plenty of memory.

I managed to upgrade to v1.4.2 using vanilla Julia; for now I got good experience. I am thankful for the authors to make this happen.

6

I’ve noticed this can happen when you have a syntax error, which is understandable.

7

that’s a great point, thank you.

But it isn’t just that. For me the worst case actually is when I’m developing code within a @testset begin ... end block. ALT+enter then just executes the entire test set, so I always have to highlight the code I want to execute, or to comment (and later again uncomment) the testset block lines.