This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-03-19
Channels
- # announcements (6)
- # aws (10)
- # beginners (73)
- # bristol-clojurians (2)
- # calva (9)
- # cider (25)
- # clj-kondo (7)
- # clojure (160)
- # clojure-dev (2)
- # clojure-europe (63)
- # clojure-italy (7)
- # clojure-nl (10)
- # clojure-uk (76)
- # clojuredesign-podcast (6)
- # clojurescript (63)
- # cursive (6)
- # data-science (3)
- # datomic (26)
- # duct (59)
- # emacs (1)
- # fulcro (12)
- # graalvm (17)
- # hoplon (23)
- # jobs-discuss (2)
- # kaocha (6)
- # meander (7)
- # off-topic (3)
- # pathom (2)
- # rdf (68)
- # re-frame (12)
- # reagent (20)
- # reitit (5)
- # ring (3)
- # ring-swagger (1)
- # shadow-cljs (14)
- # spacemacs (10)
- # sql (3)
- # tools-deps (30)
- # yada (9)
How does one get a more detailed error message for S3 anomalies?
My guess is you don't 😬 You can get the full response from the anomaly's metadata to see if there's anything else that may be interesting. What operation are you doing and what is the anomaly?
I found it. Was just (-> S3-response :Error :Message)
But it seems that it’s straight up returning a nil.
We are getting a failure in the tests in our CI but not locally. Difficult to debug this lol
I am using cognitects aws-api btw
Perhaps S3-response isn't what you expect? I suggest logging the whole anomaly map if it is one.
Had to print the whole response. Was nothing in the errors