This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-07-03
Channels
- # announcements (7)
- # beginners (114)
- # boot (5)
- # calva (25)
- # cider (26)
- # clojure (82)
- # clojure-dev (20)
- # clojure-europe (2)
- # clojure-italy (8)
- # clojure-losangeles (4)
- # clojure-norway (6)
- # clojure-uk (16)
- # clojurescript (21)
- # clojurex (3)
- # core-async (24)
- # cursive (25)
- # datomic (17)
- # emacs (5)
- # events (4)
- # fulcro (9)
- # funcool (1)
- # graalvm (4)
- # hyperfiddle (2)
- # midje (2)
- # mount (2)
- # off-topic (10)
- # pathom (11)
- # pedestal (5)
- # re-frame (36)
- # reagent (15)
- # reitit (3)
- # ring (4)
- # slack-help (2)
- # spacemacs (3)
- # sql (16)
- # tools-deps (5)
https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/core.cljc#L1100
Once again it's some odd issue with core.async + pathom + datomic + shadow-cljs
solved with -Dclojure.core.async.pool-size=500
@souenzzo do you do any blocking work in core.async loops? shouldn't be required to raise the defaults otherwise
I dont directly use core.async anythere. I'm digging a thread dump, looks like that #datomic is locking all my core.async threads
I cant block inside resolvers in parallel-parser, once everything is resolved inside a go
block
https://github.com/wilkerlucio/pathom/blob/master/src/com/wsscode/pathom/connect.cljc#L1138
I will see if is possible/make sense do this work using go
just if the resolver returns a channel