tramp-file-name-handler: Failed connect: No route to host, after remote server was shutdown
#163 opened on Jul 31, 2019
Repository metrics
- Stars
- (1,028 stars)
- PR merge metrics
- (No merged PRs in 30d)
Description
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.