This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-03-21
Channels
- # announcements (13)
- # babashka (63)
- # babashka-sci-dev (64)
- # beginners (37)
- # biff (1)
- # calva (10)
- # cider (7)
- # clj-kondo (15)
- # cljsrn (6)
- # clojure (26)
- # clojure-dev (10)
- # clojure-europe (34)
- # clojure-france (9)
- # clojure-nl (2)
- # clojure-norway (36)
- # clojure-uk (5)
- # clojurescript (142)
- # community-development (1)
- # conjure (3)
- # datalevin (5)
- # datalog (2)
- # datomic (5)
- # events (11)
- # fulcro (40)
- # gratitude (9)
- # guix (32)
- # honeysql (10)
- # jobs (2)
- # lsp (32)
- # malli (15)
- # meander (5)
- # membrane (43)
- # missionary (3)
- # nextjournal (9)
- # off-topic (38)
- # pathom (3)
- # polylith (30)
- # portal (78)
- # programming-beginners (4)
- # quil (6)
- # re-frame (20)
- # reagent (21)
- # remote-jobs (2)
- # shadow-cljs (7)
- # tools-deps (6)
- # xtdb (23)
I seem to have a 100% reproducible bug depending on whether I use Clojure 1.10.0 or Clojure 1.11.0-rc1, in combination with Puget. I don't know if this should be a library error, or something happening with Puget + Clojure. I've put together a simple repo here:
. Am I doing something wrong?
I've tested from 1.10.3 to rc1 and it looks like only rc1 exhibits this behaviour. I've update the repo with some additional information.
Well, mystery solved! It looks like somehow, somewhere, my rc1
clojure.jar
got corrupted in my .m2
repo. After blatting the directory, and causing the download of the clojure.jar
again, it seems to be a-okay! I blame the sun.
could also have been classpath caching. I would have recommended using -Sforce to ensure that wasn't the problem
well, that eliminates all the caching benefits, so makes every execution a lot slower, so I wouldn't recommend that