This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-03-03
Channels
- # bangalore-clj (2)
- # beginners (29)
- # boot (52)
- # cider (4)
- # clara (3)
- # cljs-dev (34)
- # cljsjs (7)
- # cljsrn (3)
- # clojure (71)
- # clojure-austin (1)
- # clojure-dev (5)
- # clojure-france (20)
- # clojure-russia (51)
- # clojure-spec (9)
- # clojure-uk (20)
- # clojurescript (131)
- # core-async (56)
- # core-logic (6)
- # cursive (50)
- # datascript (19)
- # datomic (16)
- # dirac (118)
- # emacs (100)
- # events (4)
- # hoplon (14)
- # incanter (1)
- # jobs (7)
- # jobs-discuss (96)
- # jobs-rus (21)
- # lein-figwheel (5)
- # leiningen (21)
- # off-topic (11)
- # om (45)
- # onyx (42)
- # pamela (1)
- # pedestal (22)
- # portland-or (3)
- # re-frame (8)
- # reagent (5)
- # ring (9)
- # robots (1)
- # spacemacs (14)
- # specter (28)
- # sql (2)
- # untangled (165)
Guys, im curious what’s the right way to do something similar to saga pattern in clojure? i have around 6 steps each with http request and i’d like to handle errors and retry on each of them
@olegakbarov what are you missing specifically to Clojure ?
im not sure that 6 level ladder of callbacks is way-to-go for me
so i guess i somehow should utilize core.async
but struggling to find reference
@olegakbarov maybe you should try to write it with synchronous code first, then use core.async to make it non-blocking
@lepistane you could try out spacemacs as it has nice defaults. It basically packages up a load of packages into layers
#spacemacs
I've followed http://acidwords.com/posts/2015-07-23-fixing-negation-in-clojure-test.html in order to have negation tests for thrown?
but everytime I call it in an assertion I get an error like the one below:
FAIL in () (form-init8859583272323518059.clj:1)
expected: (clojure.core/not ((quote api-test/thrown?) Exception {:body 12}))
actual: (not (clojure.core/not {:body 12}))
Has anyone encountered this kind of error before: JSON error (unexpected character): < I am getting this error while parsing a response. As many stackoverflow posts say , I am not parsing already parsed response
If you’re getting <
that sounds like you’re getting HTML back instead of JSON. Can you hit the same URL via curl
or in a browser to see what response you’re really getting?
Yeah, I've often seen similar things when I'm calling a web service that is supposed to return JSON, but the back-end throws an exception so it returns an HTML error page instead
@7h3kk1d hmm its not actually.. I am trying through curl as @seancorfield is suggesting to see what exactly it is returning
If not and it looks like json I’d try removing parts of it to see where the mistake is