Clojurians Log v2
Clojure programming
Channels
Apps
babashka-sci-dev 2022-03-22
borkdude 2022-03-22T13:01:15.604929Z
Unfortunately I had to revert the declarative pods commits for now because this causes image bloat
cap10morgan 2022-03-22T14:44:30.935559Z
ok, are you looking into that then? I'd need some guidance on where to even start there if you want me to.
borkdude 2022-03-22T14:47:39.448049Z
yes, of course. just need to find the time, probably next weekend
borkdude 2022-03-22T14:50:01.552709Z
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
borkdude 2022-03-22T13:01:55.893079Z
We'll have to inspect closely where this comes from. Usually this happens because of a runtime resolve or so.
cap10morgan 2022-03-22T18:05:26.648999Z
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
cap10morgan 2022-03-22T18:05:32.507419Z
hopefully will be all fixed shortly
borkdude 2022-03-22T18:07:47.826839Z
awesome :)
cap10morgan 2022-03-22T18:23:00.885799Z
fixed pods PR is up
cap10morgan 2022-03-22T20:05:41.565859Z
and all of the tests in the main PR are finally green
borkdude 2022-03-22T20:06:50.263279Z
Excellent. I'm going to take a look tomorrow. Pretty tired now after a presentation at London Clojurians :)
👍 1
borkdude 2022-03-22T13:11:56.639159Z
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
borkdude 2022-03-22T13:27:37.060449Z
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