This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-10-25
Channels
- # aws (2)
- # aws-lambda (2)
- # beginners (95)
- # boot (47)
- # cider (13)
- # clara (5)
- # cljs-dev (36)
- # cljsjs (9)
- # clojure (51)
- # clojure-austin (1)
- # clojure-greece (25)
- # clojure-italy (4)
- # clojure-japan (10)
- # clojure-russia (13)
- # clojure-spec (61)
- # clojure-uk (25)
- # clojurescript (26)
- # core-matrix (5)
- # cursive (8)
- # data-science (7)
- # datomic (43)
- # dirac (2)
- # emacs (8)
- # events (3)
- # fulcro (17)
- # graphql (29)
- # jobs-rus (4)
- # lambdaisland (4)
- # lein-figwheel (3)
- # leiningen (60)
- # luminus (15)
- # lumo (8)
- # mount (3)
- # off-topic (28)
- # om (22)
- # onyx (115)
- # other-languages (6)
- # pedestal (5)
- # re-frame (41)
- # reagent (12)
- # ring-swagger (12)
- # shadow-cljs (127)
- # unrepl (27)
- # yada (5)
I’m guessing it might be hard to reproduce - from looking at Zach’s code, you only get that WARN message on 1 in every 1024 deferreds
(https://github.com/ztellman/manifold/blob/master/src/manifold/deferred.clj#L565)
hmm, that’s literally all the logging I get (the quoted section above) - I’ve not noticed any other adverse behaviour. I suppose a custom deferred + more verbose logging of all my endpoints might reveal something - but it doesn’t look like a high priority from where I’m sitting right now.
@peterwestmacott I'm pretty sure that Yada returns another error status code instead of the 406
so you won't see any problems in your service