This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-08-22
Channels
- # announcements (13)
- # babashka (22)
- # beginners (22)
- # biff (17)
- # calva (6)
- # clerk (20)
- # clj-kondo (25)
- # clj-together (5)
- # clj-yaml (20)
- # cljdoc (16)
- # cljs-dev (1)
- # clojure (42)
- # clojure-brasil (1)
- # clojure-europe (26)
- # clojure-nl (6)
- # clojure-norway (24)
- # clojure-turkiye (3)
- # clojure-uk (5)
- # clojurescript (37)
- # core-async (7)
- # core-logic (2)
- # datalevin (7)
- # datomic (43)
- # events (2)
- # fulcro (7)
- # gratitude (1)
- # hyperfiddle (7)
- # java (7)
- # jobs (3)
- # lsp (4)
- # off-topic (16)
- # pathom (18)
- # polylith (1)
- # portal (27)
- # reitit (4)
- # releases (3)
- # shadow-cljs (47)
- # tools-build (14)
- # tools-deps (16)
- # yamlscript (11)
hey, if you use core.async consider upvoting https://ask.clojure.org/index.php/314/pub-sub-leaks-memory?show=314#q314 the jira issue has had a patch on it for 32 months now with no movement on the issue in 20 months (since it was marked "critical" in jira)
✅ 4
Upvoting is not necessary, we know there are several critical issues in core.async, which is why they are marked that way. There is only so much time in the day
well then I won't bother making an http://ask.clojure.org for ASYNC-219 so I can stump for votes there
yeah, that's not necessary
if it's at the top of https://clojure.atlassian.net/issues/?filter=10035 then that's sufficient already