This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-08-04
Channels
- # announcements (5)
- # aws (11)
- # babashka (15)
- # beginners (101)
- # biff (14)
- # calva (45)
- # clj-kondo (18)
- # cljs-dev (5)
- # clojure (178)
- # clojure-austin (5)
- # clojure-europe (8)
- # clojure-france (1)
- # clojure-nl (12)
- # clojure-norway (6)
- # clojure-spec (4)
- # clojure-uk (1)
- # clojurescript (13)
- # community-development (2)
- # conjure (6)
- # cursive (8)
- # datahike (1)
- # datalevin (3)
- # datascript (36)
- # datomic (6)
- # emacs (2)
- # etaoin (2)
- # fulcro (5)
- # graalvm (6)
- # gratitude (3)
- # introduce-yourself (1)
- # jobs-discuss (1)
- # lsp (19)
- # malli (4)
- # nbb (11)
- # off-topic (4)
- # other-languages (1)
- # pathom (19)
- # pedestal (1)
- # shadow-cljs (22)
- # spacemacs (16)
- # tools-deps (31)
- # vim (7)
i’m not sure if this was reported before but this started happening when using the Socket REPL since the latest EAP. i usually see these after my computer wakes up from the sleep mode, if that helps:
Hmm, I’ll take a look at that. Some of the connection code changed in the latest EAP to support picking up the port from a file, but that shouldn’t affect the connection once established.
Just to clarify, you mentioned that you see this after your computer wakes up from sleep, but do you see this on a new connection after it wakes up, or is it an existing REPL that you opened before putting the computer to sleep?
Did that definitely work in previous versions? I can’t see anything that has changed that might have caused that.
Ah, yes, that looks like it might be the same issue, and the sleeping is a red herring. I filed an issue, but it turns out there already was one: https://github.com/cursive-ide/cursive/issues/2603. I’ve moved that to the current EAP series.