I found this video quite helpful: https://youtu.be/islMjv55cN8

Try just using shadow-cljs jack-in instead of deps+shadow for the cljs side. I think that gives a better experience. (Shadow CLJS will still look to deps.edn for deps, as instructed by the shadow-cljs.edn). Then if you also need a repl for the server, open that in a separate VS Code window. Instructions https://calva.io/workspace-layouts/ to help getting the same project open in 2 windows.

Thanks, @U03DBC3BGAV! I was just about to post that. There is also this article: https://blog.agical.se/en/posts/shadow-cljs-clojure-cljurescript-calva-nrepl-basics/

@U042LKM3WCW can you describe more about: > anytime I need to do something outside of [calvas jack in], the whole app configuration falls apart Maybe that can give us ideas about more directed help.

"There is also this article: https://blog.agical.se/en/posts/shadow-cljs-clojure-cljurescript-calva-nrepl-basics/" Gonna be reading that too tomorrow. Looks very helpful, thanks!

Thanks, I have been having the same problem and now I have some reading to do.

@U02DLFAV2KV Can you share a bit about the problem? I'd like to learn a bit about how this thing works out there. Especially about when it doesn't work.

@U0ETXRFEW I am working on a repo that has the front and back together. There is a deps.edn and a shadow-cljs.edn. When we started working I would launch npx shadow-cljs watch app on the terminal and then I could either jack-in (ctr-alt +c + ctr-alt+j) to the clj repl with deps or connect (ctr-alt +c + ctr-alt+c) to the cljs repo on the running shadow-cljs. This sort of worked: I could only interact with one repl at a time, but both were running in the background and I could easily switch between them. Then about a week or two ago, that stoped working and I could no longer switch to beteew the repls. What I mean is that the only repl that would work, was the first one I connected to. If I tried to switch, the output in the output window said that I was connected, but the status bar indicator showed that I was not connected and there was no interactivity. Which meant that if I had the server running I had no cljs repl, and if I started the cljs repl, the server which was running in the clj repl, would stop working. I have tried both suggestions mentioned above in the thread and both work great. I am currently using two vs code workspaces. The colleague I work with uses cider/spacemacs, so I am waiting to see if the {:deps true} in shadow-cljs.edn works for him as that is the simplest to use. By the way, both the video and the article were very helpful and clear in explaining why I was having the problem and in giving a more complex explanation of how the calva->repl connection works. Thank you !!🎉

Thanks!

I wonder why you are using two workspaces? I would just use one, jack-in to shadow-cljs and then Calva should connect both REPLs and for .clj files use the clj repl, for .cljs files the cljs repl and for .cljc files I get to choose which repl via the toggle (I use the toolbar button for this).

Right now I am in a transition phase. I have a branch where I have setup dps.edn and shadosw-cljs.edn to work so that I only have to one jack-in to shadow-cljs ( :deps true and all dependencies in deps.edn). In this branch I can do as you mentioned above, but I am waiting to see if that works for my colleague before pushing to main. In the meantime, main has the ’old setup with the dependencies separate in the deps and shadow-cljs, I can have both repls running, each one in its workspace, as indicated in the calva doc. I have to have and extra window open, but it works. In this setup, when I jack-in to shadow-cljs the cljrepl works, but since it does not have any of the deps.edn dependencies (because shadow-cljs does not have :deps true ), it’s not really useable. When try to evaluate anything, I get missing dependency errors. I hope it is clear 😜

Thanks! Yes, clearer. It should totally work for your CIDER wielding colleague. But we'll see, I guess. 😃

I don’ see why it would not, it’s more about process.

Certainly. Plain manners.

Then I have this in my .ssh/config to connect to the remote port and forward it as a local port:

Host **hostname is here**
  HostName **hostname is here**
  LocalForward 50001 localhost:54654

I figure then that I should be able to jack-in with calva "Connect to a running REPL in your project". I tried selecting project type generic or deps.edn and then connect to localhost:50001 but neither is working. Thanks a lot for any help!

I figure my next step might be to have the project running locally and see if I can jack-in locally through the exposed port.

Another next step is to remove Calva from the picture and connect to the nREPL server using something like:

clojure -Sdeps '{:deps {reply/reply {:mvn/version "0.5.1"}}}' -M -m reply.main --attach 54654 

clojure -Sdeps '{:deps {reply/reply {:mvn/version "0.5.1"}}}' -M -m reply.main --attach `< .nrepl-port

The VS Code Remote Extension is also very powerful. Then you run the VS Code instance on that server and your local VS Code is more of a client. A very seamless experience.

For some reason I am unable to connect to the nREPL. clojure -Sdeps '{:deps {reply/reply {:mvn/version "0.5.1"}}}' -M -m reply.main --attach 8080 SocketException The transport's socket appears to have lost its connection to the nREPL server nrepl.transport/bencode/fn--716/fn--717 (transport.clj:122) nrepl.transport/bencode/fn--716 (transport.clj:122) nrepl.transport/fn-transport/fn--670 (transport.clj:50) clojure.core/binding-conveyor-fn/fn--5823 (core.clj:2047) java.util.concurrent.FutureTask.run (FutureTask.java:317) java.util.concurrent.ThreadPoolExecutor.runWorker (ThreadPoolExecutor.java:1144) java.util.concurrent.ThreadPoolExecutor$Worker.run (ThreadPoolExecutor.java:642) java.lang.Thread.run (Thread.java:1589) Bye for now!

It seems like port forwarding is working as I would expect. I find that if I can forward port 80 from my remote server to my local computer's port 8080 using the same syntax in the ssh config and then am able to connect to the http server with my browser at localhost:8080.

Have you tried using the Remote Extension? (Given that you can install VS Code on the remote host, of course.)

Maybe some security mechanism stops ”high” port numbers from being forwarded...

You could try telnet maybe. I think it might provide better clues than that nREPL client stack trace does.

telnet -4 localhost 61456
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.

Above is a connection to a working local nrepl

that is all the output I see then it appears to be waiting for something

And what do you get with the remote server?

when trying to connect to local forwarded port (now I am forwarding to 8080):

telnet localhost 8080
Trying ::1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

I'll try a lower port number on the remote machine and see if that helps

I changed to a lower port number on the remote server to see if that helped. No joy. :-(

telnet -4 localhost 8080
Trying 127.0.0.1...
telnet: connect to address 127.0.0.1: Connection refused
telnet: Unable to connect to remote host

Maybe try starting the nREPL server on port 80 and forward that?

Not as a solution, but as a diagnostics data point.

Still no joy with the nrepl server listening on port 80.

❯ telnet -4  80
Trying 176.58.115.27...
telnet: connect to address 176.58.115.27: Connection refused
telnet: Unable to connect to remote host

❯ telnet -4 localhost 8080
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

But jetty is responding on 8080 where I moved it to.

Time to try try the remote host VSCODE extension. I tried it before but since I have my clojure running in docker I will have to install java again outside the docker image.

> But jetty is responding on 8080 where I moved it to. Hmmm, I'm sure this is a clue as well, but I fail to understand it. 😃

I have the remote extension apparently working great through ssh but still cannot jack in after installing java remotely.

absolute minimal code for an embedded nrepl server explicitly included in code. It works fine on my local machine. And I can run the other code with the nrepl embedded with the web server and I can connect no problem on my local machine. https://github.com/jamiepratt/embedded-repl

I've found the issue, problem with my docker syntax it seems but don't know how to fix: https://serverfault.com/questions/1116621/how-do-i-open-ports-on-a-docker-image

Not sure if this is an issue but I see in the docker docs (and in a work project) that the ports are stated like so:

ports:
      - "8000:8000"

ports:
      - 127.0.0.1:2001:2001

ports:
      - "2001:2001"