Clojurians Log v2
Clojure programming
Channels
Apps
clojure-dev
dharrigan 2022-03-21T09:29:47.875739Z
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:
dharrigan 2022-03-21T12:47:01.301719Z
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.
dharrigan 2022-03-21T13:36:43.974599Z
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.
😅 1
dharrigan 2022-03-21T13:37:01.361849Z
I've never seen that happen before!
Alex Miller (Clojure team) 2022-03-21T14:33:36.246969Z
could also have been classpath caching. I would have recommended using -Sforce to ensure that wasn't the problem
dharrigan 2022-03-21T15:27:28.571249Z
Interestingly, I always do that as my alias in my shell.
dharrigan 2022-03-21T15:28:08.881009Z
(i.e., I've aliased clojure to clojure <a bunch of stuff> -Sforce .....
Alex Miller (Clojure team) 2022-03-21T15:33:09.590539Z
well, that eliminates all the caching benefits, so makes every execution a lot slower, so I wouldn't recommend that
dharrigan 2022-03-21T15:45:30.423749Z
True true. It's a hang over from when i was trying some stuff out, I'll look to remove it.
adi 2022-03-22T05:19:40.821839Z
TIL -Sforce. This is the dark S of the Force.
😎 1