This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2024-05-08
Channels
- # announcements (14)
- # babashka (16)
- # beginners (15)
- # biff (15)
- # calva (48)
- # clj-kondo (42)
- # cljdoc (25)
- # clojure (18)
- # clojure-europe (75)
- # clojure-nl (1)
- # clojure-norway (19)
- # clojure-romania (1)
- # clojure-uk (10)
- # conjure (18)
- # core-typed (4)
- # cursive (16)
- # emacs (8)
- # fulcro (27)
- # graalvm (17)
- # honeysql (14)
- # hyperfiddle (9)
- # lsp (24)
- # missionary (5)
- # music (1)
- # nrepl (20)
- # off-topic (14)
- # re-frame (9)
- # reagent (34)
- # reitit (2)
- # releases (1)
- # shadow-cljs (19)
- # sql (16)
- # squint (9)
- # testing (2)
- # tools-build (10)
I keep getting
; Sponsored by @trev-dev ❤
; --------------------------------------------------------------------------------
; localhost:52680 (ECONNREFUSED): .nrepl-port
; --------------------------------------------------------------------------------
; localhost:52680 (disconnected): .nrepl-port
After something odd happened in nvim and I force quit it.I did killall nvim
successfully. But now I can't connect to the Conjure repl.
It's a small babashka project.
Maybe there's a rogue Conjure process I need to kill?
Doesn't matter if I change the port.
Is there by chance an .nrepl-port
file still in your filetree?
Yes, that's where I changed the port
try and rm that file?
Now I started a babashka repl in a different way,
nrepl {:requires ([babashka.fs :as fs]
[babashka.nrepl.server :as srv])
:task (do (srv/start-server! {:host "localhost"
:port 1339})
(spit ".nrepl-port" "1339")
(-> (Runtime/getRuntime)
(.addShutdownHook
(Thread. (fn [] (fs/delete ".nrepl-port")))))
(deref (promise)))}}
(from our bb.edn
)
and it seems to connect fine to that
I made do with that server. Thanks, @U0482NW9KL1 🙂
Guess I'll have to reboot at some point, and that'll fix my problem, I assume
👋 , yea the .nrepl-port file not getting cleared on an abnormal exit has bitten me many a timee
FYI @U0AQ3HP9U, the .nrepl-port
file is just where the current port is stored for other tools to pick up on
One of my team mates made that bb.edn. Maybe his setup requires knowing the port.