Clojurians Log v2
Clojure programming
Channels
Apps
ring
R.A. Porter 2022-01-17T19:32:14.007Z
I'm seeing an error when upgrading to 🧵
Edit: it's custom library code. Ignore me.1.9.5, but haven't been able to track down the specifics of it yet.
R.A. Porter 2022-01-17T19:33:45.007100Z
I can update all of my app's ring dependencies from 1.9.4 -> 1.9.5 except for ring/core. The exception I'm seeing is...
java.lang.Thread.run Thread.java: 829
org.eclipse.jetty.util.thread.QueuedThreadPool$Runner.run QueuedThreadPool.java: 1034
org.eclipse.jetty.util.thread.QueuedThreadPool.runJob QueuedThreadPool.java: 883
org.eclipse.jetty.io.ChannelEndPoint$1.run ChannelEndPoint.java: 104
org.eclipse.jetty.io.FillInterest.fillable FillInterest.java: 105
org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded AbstractConnection.java: 311
org.eclipse.jetty.server.HttpConnection.onFillable HttpConnection.java: 277
org.eclipse.jetty.server.HttpChannel.handle HttpChannel.java: 392
org.eclipse.jetty.server.HttpChannel.dispatch HttpChannel.java: 645
org.eclipse.jetty.server.HttpChannel.lambda$handle$1 HttpChannel.java: 400
org.eclipse.jetty.server.Server.handle Server.java: 516
org.eclipse.jetty.server.handler.HandlerWrapper.handle HandlerWrapper.java: 127
ring.adapter.jetty.proxy$org.eclipse.jetty.server.handler.AbstractHandler$ff19274a.handle
ring.adapter.jetty/proxy-handler/fn jetty.clj: 28
ring.util.servlet/update-servlet-response servlet.clj: 98
ring.util.servlet/update-servlet-response servlet.clj: 109
ring.core.protocols/eval4577/fn/G protocols.clj: 8
clojure.core/-cache-protocol-fn core_deftype.clj: 583
java.lang.IllegalArgumentException: No implementation of method: :write-body-to-stream of protocol: #'ring.core.protocols/StreamableResponseBody found for class: clj_elastic_apm.support$deferred_transaction_body$reify__8493R.A. Porter 2022-01-17T19:34:19.007300Z
As I said, other than determining that it is just the ring/core dependency that's giving me the issue, I haven't tracked down the problem yet.
R.A. Porter 2022-01-17T19:55:03.007500Z
I'm starting to think it's a problem with one of my team's custom libraries. Looking a bit more.