Cursive 2025.2.1-eap7 is out. It's a bugfix release, fixing a couple of issues reported in the tracker. https://cursive-ide.com/blog/cursive-2025.2.1-eap7.html
I'm getting a lot of
REPL startup failed:
No nREPL connection details received
on REPL startup. Like maybe 50% of the time? That seems like a lot.shortly after startup, and sometimes after successfully evaluationg 3 or 4 (long-ish running) forms at the REPL.
Sorry, when you say: > shortly after startup, and sometimes after successfully evaluationg... Isn't the problem when the REPL actually starts? i.e. before you eval anything?
Sometimes before, sometimes after
Does your REPL take a long time to start up? If so, there's a setting at Settings | Languages & Frameworks | Clojure | REPL | REPL startup timeout which you can increase.
So you can get that error after the REPL has started and is working? That's very odd, I'll look at that. Do you get the message that the REPL has started, or are you evaluating before that happens?
I think (am afk now) that it was appearing to start normally, then some time after I had assumed everything was fine and began using it it would fail.
Possibly relevant that I was restarting my repl a lot today
So it was almost certainly after a restart every time
And I was also getting some restarts that didn't appear to work
Ok. I'm about to be afk for a bit but will look when I get back. I'd be interested to know how long your REPL takes to start, i.e. to display the repl started message, when you get a chance.
In general, no my repl doesn't take a long time to start up. I'm long out of the habit of dumping much in the user ns.
Ok, very strange then.
I'll try and observe more closely tomorrow
It's not a high priority really. Just a bit odd and annoying occasionally
Yes definitely.
Mostly I don't restart my repl that often!
i was observing this error too, sporadically, even with earlier versions of cursive. to me it seemed to happen, when i've restarted an already running repl (which has "Allow multiple instances" turned off) and i was impatient and attempted to load namespaces before the repl has fully started again.