Julia vscode with remote-ssh ENAMETOOLONG

grunst · June 20, 2024, 3:56pm

Trying to use julia vscode extension with remote-ssh I get

ERROR: LoadError: IOError: connect: name too long (ENAMETOOLONG)
Stacktrace:
 [1] wait_connected(x::Base.PipeEndpoint)
   @ Sockets /usr/local/apps/julia/1.10.0/share/julia/stdlib/v1.10/Sockets/src/Sockets.jl:528
 [2] connect
   @ /usr/local/apps/julia/1.10.0/share/julia/stdlib/v1.10/Sockets/src/Sockets.jl:563 [inlined]
 [3] connect
   @ /usr/local/apps/julia/1.10.0/share/julia/stdlib/v1.10/Sockets/src/PipeServer.jl:103 [inlined]
 [4] serve(args::String; is_dev::Bool, crashreporting_pipename::String)
   @ VSCodeServer ~/.vscode-server/extensions/julialang.language-julia-1.79.2/scripts/packages/VSCodeServer/src/VSCodeServer.jl:113
 [5] top-level scope
   @ ~/.vscode-server/extensions/julialang.language-julia-1.79.2/scripts/terminalserver/terminalserver.jl:47
in expression starting at /home/fars/.vscode-server/extensions/julialang.language-julia-1.79.2/scripts/terminalserver/terminalserver.jl:20

ERROR: LoadError: IOError: connect: name too long (ENAMETOOLONG)

Adding a println.(args) on line 22 of terminalserver.jl gives

/etc/ecmwf/ssd/ssd1/tmpdirs/user.3371913.20240620_152946.442/vsc-jl-repl-a7fed03e-0383-4fb5-b056-9c5c339082d7
/etc/ecmwf/ssd/ssd1/tmpdirs/user.3371913.20240620_152946.442/vsc-jl-cr-5424b91d-00cd-4175-937b-87c0ac093867
USE_REVISE=true
USE_PLOTPANE=true
USE_PROGRESS=true
ENABLE_SHELL_INTEGRATION=true
DEBUG_MODE=false

The first one is used as the socket and is 110 characters which is indeed too long (e.g. remark in PipeServer.jl)

github.com

JuliaLang/julia/blob/0a491e00a1f38b814ca173bd7d9bffeadde65738/stdlib/Sockets/src/PipeServer.jl#L74


      
              server.status = StatusOpen
              iolock_end()
              return true
          end
          
          """
              listen(path::AbstractString) -> PipeServer
          
          Create and listen on a named pipe / UNIX domain socket.
          
          !!! note
              Path length on Unix is limited to somewhere between 92 and 108 bytes (cf. `man unix`).
          """
          function listen(path::AbstractString)
              sock = PipeServer()
              bind(sock, path) || throw(ArgumentError("could not listen on path $path"))
              return listen(sock)
          end
          
          function connect!(sock::PipeEndpoint, path::AbstractString)
              iolock_begin()

Is there any workaround or way to control the name that the vscode extensions uses for these socket?

pfitzseb · June 24, 2024, 10:04am

There is not. I don’t think there’s any real making the name user-controllable – there are only two constraints for it after all: being valid (i.e. short enough) and being unique.

grunst · June 24, 2024, 1:10pm

Thanks for creating the issue!
If others run into this. If the path is just a few characters to long you can

cd ~/.vscode-server/extensions/julialang.language-julia-1.79.2/dist
sed -i 's/vsc-jl-repl/v/g' extension.js
sed -i 's/vsc-jl-repl/v/g' extension.js.map

bmwilly · December 20, 2024, 11:47am

@grunst thanks, this hack finally allowed me to open a Julia REPL

FWIW, I had the same issue and used the same hack with the client-side extension in ~/.vscode/.

Topic		Replies	Views
REPL errors when started from VSCode (connected to a server via remote SSH) General Usage repl , vscode	1	259	September 22, 2023
Julia 0.6 add remote workers error New to Julia parallel , cluster	3	994	June 27, 2017
VS Code Julia extension crash when starting up (Windows 10 fall creator update) VS Code	2	1875	October 31, 2017
VS Code Extension woes Offtopic	11	2056	September 13, 2017
Remote development using VSCode tip VS Code	9	3396	May 6, 2021

Julia vscode with remote-ssh ENAMETOOLONG

Related topics