Clojurians Log v2

Calva fails connecting to the nrepl server of this version. With v0.7.30:

nREPL server started on port 31337...
:msg "{:value \"#object[Ps user]\", :id \"1\", :session nil, :ns \"user\"}"
:msg "{:status [\"done\"], :id \"1\", :session nil, :ns \"user\"}"
:msg "{:versions {\"sci-nrepl\" {\"major\" \"0\", \"minor\" \"0\", \"incremental\" \"1\"}}, :ops {\"complete\" {}, \"info\" {}, \"lookup\" {}, \"eval\" {}, \"load-file\" {}, \"describe\" {}, \"close\" {}, \"clone\" {}, \"eldoc\" {}}, :status [\"done\"], :id \"3\", :session \"25a8a46e-a6a6-442f-bf44-eeac75c440ba\", :ns \"user\"}"
:msg "{:status [\"no-eldoc\" \"done\"], :err \"Message should contain a `sym`\", :id \"7\", :session \"25a8a46e-a6a6-442f-bf44-eeac75c440ba\", :ns \"user\"}"

nREPL server started on port 31337...
:msg "{:value \"#object[Ps user]\", :id \"1\", :session nil, :ns \"user\"}"
:msg "{:status [\"done\"], :id \"1\", :session nil, :ns \"user\"}"
:msg "{:op :describe, :id \"3\", :verbose 1, :session \"bce49eca-8ac1-4d51-bb3b-6538740e82fa\", :status [\"error\" \"done\"], :err \"unknown-op\", :ns \"user\"}"
Client closed connection.
nREPL server started on port 31337...
Client closed connection.

I should make Calva more resilient, but anyway.

I tested it on the Apropos podcast last Tuesday :)

with lein test and emacs

have you also upgrade sci.nrepl?

d

The doc/nrepl project in scittle is the reference project that should work

Yes, updated both. Probably emacs and lein do not throw in the towel when describe fails.

can you debug why it fails?

I can try.

It’s that the describe op has been removed from the browser side of things and moved to the browser-nrepl relay. So updating Scittle version also means updating browser-nrepl coordinates. Also there doesn’t seem to be maven coord for the new browser-nrepl, so need to use git coords for now.

that's what I mean with did you upgrade sci.nrepl

do you need a mvn release

can you test the git version first?

Yeah, I misunderstood about sci.nrepl. Read it as scittle.nrepl 😃 I don’t need an mvn release, btw. Just something I noticed because my bb tasks were using mvn.

Now I need to figure out why Epupp does not want to connect to the new relay.