Closed pesterhazy closed 2 weeks ago
Which version mix is this? shadow-cljs? core.async? undertow?
My first, and really only, guess is some sort of version conflict. Or something else messing with classloaders.
This is the websocket handling loop which uses core.async.
If you have something to reliably reproduce this I'm happy to take a look, otherwise I'm afraid there is nothing much I can do.
org.clojure/clojurescript 1.11.60 (EPL-1.0)
org.clojure/core.async 1.5.648 (EPL-1.0)
thheller/shadow-client 1.3.3 (EPL-1.0)
thheller/shadow-cljs 2.25.5 (EPL-1.0)
thheller/shadow-cljsjs 0.0.22 (EPL-1.0)
thheller/shadow-undertow 0.3.1 (EPL-2.0 OR GPL-2.0-or-later WITH Classpath-exception-2.0)
thheller/shadow-util 0.7.0 (EPL-1.0)
io.undertow/undertow-core 2.2.4.Final (Apache-2.0)
I'll try and update core.async and see if that helps
Not necessary, this is the correct intended core.async version. The rest seems correct too.
That leaves anything messing with Classloaders, the JVM in general or maybe clojure itself such as tools.namespace. No real actual guess though from my end.
This exception happens rarely (about once a day) when running the dev env for our browser code
I think this is related to websocket handling code
Reminiscent of https://github.com/thheller/shadow-cljs/issues/175
Full stacktrace here: stacktrace.txt