search

emacs-jupyter / jupyter

An interface to communicate with Jupyter kernels.
GNU General Public License v3.0
933 stars 92 forks source link

tramp-file-name-handler: Failed connect: No route to host, after remote server was shutdown #163

Open vv111y opened 5 years ago

vv111y commented 5 years ago

The Problem: I shutdown the remote server and this error comes up even when trying to do helm-M-x (this is what spacemacs uses for M-x). It keeps popping up in other interactions.

Instrumenting tramp-file-name-handler gives me Result: ("DESCRIPTION" "/jpy:192.168.0.35#8888:/") when (let ((filename (apply 'tramp-file-name-for-operation operation args))) is evaluated.

192.168.0.35 is the LAN ip of the remote box I was working on. So somehow the jpy connection is still in there somewhere causing problems.

the Praise: This is looking really good. I didn't bother with ssh tunnel or copying the session .json file. I just opened up the jupyter server to my lan and I could connect by specifying the lan ip address, no problem. I can start kernels and repls.
Also, I could associate emacs buffers to the repls that were connected to the remote kernel. No issue such as (https://github.com/dzop/emacs-jupyter/issues/49) or (https://github.com/dzop/emacs-jupyter/issues/156). This is promising to be a great experience - Big Thank You.

nnicandro commented 5 years ago

Do you know what the default-directory was whenever you get the error? Was it /jpy:192.168.0.35#8888:/?

Also can you evaluate (setq tramp-debug-on-error t) and show the backtrace whenever the error happens.

Big Thank You

Your welcome.

nnicandro commented 4 years ago

@vv111y Are you able to reproduce the issue and, if so, were you able to get a more useful backtrace with my suggestion?

vv111y commented 4 years ago

Sorry for delay, I'm looking now...