This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-09-19
Channels
- # aws (2)
- # beginners (135)
- # boot (20)
- # chestnut (7)
- # cider (18)
- # clara (5)
- # cljs-dev (50)
- # cljsrn (30)
- # clojure (252)
- # clojure-italy (9)
- # clojure-losangeles (5)
- # clojure-russia (8)
- # clojure-spec (33)
- # clojure-uk (5)
- # clojurescript (32)
- # clr (4)
- # cursive (5)
- # data-science (1)
- # datascript (1)
- # datomic (40)
- # emacs (1)
- # fulcro (18)
- # graphql (11)
- # hoplon (3)
- # lein-figwheel (2)
- # lumo (47)
- # off-topic (2)
- # om-next (3)
- # onyx (10)
- # pedestal (22)
- # protorepl (6)
- # re-frame (7)
- # reagent (38)
- # ring (1)
- # ring-swagger (5)
- # rum (3)
- # spacemacs (19)
- # specter (5)
- # vim (13)
- # yada (16)
I'm trying to consume some transit sent by a Yada server by an aleph http client. Is there some tools in yada I can use to read the transit data while keeping everything async?
I tried using yada.request-body/parse-stream, but I can't get it to work. 😕
Oh wait it does work, but only once.
@frozenlock I thinking reading from a stream is like reading from a core async buffer: it has side effects
Should I expect any breaking changes when upgrading from yada 1.2.2 to 1.2.9 except for the arity of the response function?
The arity has not changed. The only thing is that you must use a single arity as usual and no other arities are supported
hello, has anyone come across this message?
java.io.IOException: File name too long, compiling:(yada/schema.clj:84:3)
Exception in thread "main" java.io.IOException: File name too long, compiling:(yada/schema.clj:84:3)
I was just running lein uberjar
and got this. But it works fine with lein run
@igorgarcia is this on the most recent yada?
[yada "1.2.0"]
let me try upgrading it
@igorgarcia https://github.com/juxt/yada/pull/147 it's this I think
upgrading to 1.2.9 solved the problem. Thanks @dominicm
I always run lein ancient
, dunno why I didn't do it this time. Just caught bidi was also outdated.