"Cannot find class completion initialisation file"

21 views
Skip to first unread message

Blake Watson

unread,
Oct 3, 2021, 5:03:09 PM10/3/21
to cur...@googlegroups.com
Getting this error in Cursive repls:
```
Connecting to local nREPL server...
Cannot find class completion initialisation file
Clojure 1.10.1
Error updating class definitions:
Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass (URLClassLoader.java:435).
cursive.repl.runtime.class
nREPL server started on port 56400 on host 127.0.0.1 - nrepl://127.0.0.1:56400
```
New apps, old apps...doesn't seem to hurt anything but it's noisy.

===Blake===

Blake Watson

unread,
Oct 3, 2021, 6:07:38 PM10/3/21
to cur...@googlegroups.com
To elaborate a little bit, those errors come up with every command entered in the REPL. So it's VERY noisy.
```
Cannot find class completion initialisation file
Clojure 1.10.1
Error updating class definitions:
Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass (URLClassLoader.java:435).
cursive.repl.runtime.class
nREPL server started on port 52135 on host 127.0.0.1 - nrepl://127.0.0.1:52135
(+ 1 1)
=> 2

Error updating class definitions:
Execution error (ClassNotFoundException) at java.net.URLClassLoader/findClass (URLClassLoader.java:435).
cursive.repl.runtime.class
```

Colin Fleming

unread,
Oct 7, 2021, 5:09:34 PM10/7/21
to Cursive Group
This is very strange. I can't see why that would ever happen. This is when the REPL is initialised and it's loading the code that it will use for later completions. Those files should always be present, and if they're not everyone using that version should see that error. Which version of Cursive are you using?
--
You received this message because you are subscribed to the Google Groups "Cursive" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cursive+u...@googlegroups.com.

Blake Watson

unread,
Oct 9, 2021, 3:33:41 PM10/9/21
to cur...@googlegroups.com
Cursive 1.11.0-2021.2 on IJ 2021.2.2

I did the "invalidate caches" thing. That seems to have done the trick.

Reply all
Reply to author
Forward
0 new messages