This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-22
Channels
- # announcements (16)
- # babashka (7)
- # babashka-sci-dev (14)
- # beginners (34)
- # calva (80)
- # clj-kondo (23)
- # cljdoc (17)
- # cljs-dev (1)
- # cljsrn (10)
- # clojure (51)
- # clojure-berlin (3)
- # clojure-europe (14)
- # clojure-italy (10)
- # clojure-nl (2)
- # clojure-norway (211)
- # clojure-uk (5)
- # clojurescript (4)
- # cursive (22)
- # datalevin (12)
- # datomic (2)
- # defnpodcast (1)
- # duct (5)
- # emacs (4)
- # events (2)
- # fulcro (3)
- # graalvm (1)
- # interop (3)
- # introduce-yourself (4)
- # java (1)
- # jobs (7)
- # kaocha (38)
- # leiningen (3)
- # lsp (11)
- # malli (4)
- # membrane (5)
- # music (1)
- # off-topic (28)
- # pathom (13)
- # pedestal (3)
- # polylith (4)
- # portal (10)
- # practicalli (1)
- # re-frame (33)
- # reitit (2)
- # remote-jobs (1)
- # sci (6)
- # shadow-cljs (49)
- # sql (4)
- # xtdb (3)
Unfortunately I had to revert the declarative pods commits for now because this causes image bloat
ok, are you looking into that then? I'd need some guidance on where to even start there if you want me to.
if you want to take a stab at this yourself, just start from the state before the commit and slowly add things, then recompile and see if compilation gets slower and the binary gets a lot bigger
We'll have to inspect closely where this comes from. Usually this happens because of a runtime resolve
or so.
yep, I think I found it and that was it. and it's just a bug. there was a reference to a local symbol resolve
but when I extracted the referencing code out into its own fn, I didn't notice that and it just silently started referencing clojure.core/resolve
hopefully will be all fixed shortly
fixed pods PR is up
and all of the tests in the main PR are finally green
Excellent. I'm going to take a look tomorrow. Pretty tired now after a presentation at London Clojurians :)
I'm sorry about that, but I'm happy I catched that. I thought it was related to trying out the m1 / graalvm 22 but luckily it wasn't that
Since I now have an m1 build of babashka (try the m1 branch + https://github.com/babashka/babashka/wiki/Compiling-for-M1) I see that it cannot load intel pods. Perhaps we should fall back on those, if they are able to run in macos