Fork me on GitHub

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.

😅 1

I've never seen that happen before!

Alex Miller (Clojure team)14:03:36

could also have been classpath caching. I would have recommended using -Sforce to ensure that wasn't the problem


Interestingly, I always do that as my alias in my shell.


(i.e., I've aliased clojure to clojure <a bunch of stuff> -Sforce .....

Alex Miller (Clojure team)15:03:09

well, that eliminates all the caching benefits, so makes every execution a lot slower, so I wouldn't recommend that


True true. It's a hang over from when i was trying some stuff out, I'll look to remove it.


TIL -Sforce. This is the dark S of the Force.

😎 1