This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-03-08
Channels
- # announcements (6)
- # beginners (100)
- # calva (17)
- # cljs-dev (31)
- # cljsrn (2)
- # clojars (3)
- # clojure (137)
- # clojure-australia (1)
- # clojure-europe (41)
- # clojure-gamedev (3)
- # clojure-italy (1)
- # clojure-nl (3)
- # clojure-poland (16)
- # clojure-serbia (7)
- # clojure-taiwan (1)
- # clojure-uk (10)
- # clojurescript (10)
- # cursive (25)
- # data-oriented-programming (4)
- # datomic (26)
- # fulcro (39)
- # graalvm (6)
- # jobs (2)
- # jobs-discuss (2)
- # kaocha (19)
- # klipse (1)
- # leiningen (3)
- # lsp (18)
- # malli (21)
- # meander (26)
- # off-topic (29)
- # pathom (39)
- # polylith (3)
- # practicalli (2)
- # re-frame (11)
- # reitit (8)
- # rewrite-clj (7)
- # sci (11)
- # shadow-cljs (44)
- # sql (8)
- # tools-deps (32)
- # xtdb (3)
I just had a weird bug, and even though it's fixed, I don't understand what's going on: The bug was that I had written an event handler with reg-event-fx, and only returned a :dispatch key, no :db. The thing is: it worked fine, so I guess I tried it and found that it's not necessary to type the extra :db a few times. But now I registered a global event handler, and suddenly things were going wrong, since the effects db was nil. I suppose there's a mechanism that copies the db if the effects db isnt there at the end of the chain? Is that something well known?
It is well known: https://github.com/day8/re-frame/blob/fd12bd3a2c92aae62508071c7b70f95e8eaa58fb/docs/Effects.md#db-not-always-needed Why it wasn't working with a global interceptor depends on what exactly was going on in that interceptor.
Ah yeah, thanks. As always, reading the docs better would have solved it 🙂
I’m running into an Eval timed out!
error message when trying to sub
some but not all of my subscriptions. Seems to be the ones with a lot of data, also seems to be associated with the error (which appears in nrepl buffer) WARN - Max payload length 4m, get: 4322857
, which i think is a websocket-related warning? Kind of stumped by this one. I’ve tried the easy stuff like lein clean
and restart repl, but no luck. This started happening recently too…
no, when I try to run the same subscription in the connected figwheel repl. Sorry, I should have mentioned that. The subs appear to work fine in the actual application, that is the functionality that relies on the subs works.
After doing a quick profile in chrome devtools, it indeed seems like there is an extremely large amount of pprint
thrash