Not supported: class org.eclipse.jetty.client.HttpResponseException

[holyjak]

I get the following error (I believe when trying to access an S3 bucket I am not authorized to access), which seems to indicate the pod is missing classes representing (some) exceptions (notice the last line):

"ERROR: can't serialize to transit:" {:cognitect.anomalies/category :cognitect.anomalies/fault, :cognitect.anomalies/message "Invalid 'Location' header: null", :cognitect.http-client/throwable #error {
 :cause "Invalid 'Location' header: null"
 :via
 [{:type org.eclipse.jetty.client.HttpResponseException
   :message "Invalid 'Location' header: null"
   :at [org.eclipse.jetty.client.HttpRedirector redirect "HttpRedirector.java" 167]}]
 :trace
 [[org.eclipse.jetty.client.HttpRedirector redirect "HttpRedirector.java" 167]
  ...]
java.lang.Exception: Not supported: class org.eclipse.jetty.client.HttpResponseException [at <repl>:1:354]

When I print *e it contains many things, including

{:type clojure.lang.ExceptionInfo
   :message "java.lang.Exception: Not supported: class org.eclipse.jetty.client.HttpResponseException"
   :data {:type "class java.lang.RuntimeException"}
   :at [babashka.pods.impl$processor invokeStatic "impl.clj" 154]}

[borkdude]

That makes sense. Everything that goes over the wire from bb to the pod and vice versa is serialized using transit and exceptions can't be properly serialized. We should come up with a good workaround.

[holyjak]

Some clojurification of the exception data?

#exception{:message "I failed"
                    :class "org.eclipse.jetty.client.HttpResponseException"
                   :stacktrace [...]}

[borkdude]

@holyjak yeah, I think that would be good.

[borkdude]

Fixed in next release.