Clojurians Log v2

lein 2.9 and lein-ring-server do not place nicely

reverting to self-installed 2.8.3 and all is ok

@chadhs haven’t tried, but what error?

@mikerod https://gist.github.com/chadhs/02b6760ea1c449fe695e166b5232cb6a

there’s my project.clj and the output when i run lein ring server

ah weird that the lein version affected that

at least it seems weird to me at first glance

looks like a clj version would be the cause of a spec failing in clojure.core

the only reason i thought to try brew uninstalling lein and manually grabbing 2.8.3 was due to the fact the only thing i changed since i worked on that project last was updating homebrew stuff today and noticed the new lein release

and that error message looked more daunting than the oauth stuff i was about to look at in my project so i gave up pretty quickly 😬

@mikerod for now i just made a quick install-lein.sh $version script so i can grab whatever i want into ~/bin rather than rely on homebrew for now.

@chadhs I’ve used brew switch to toggle between them I think

have to have both installed in cellar

but either way.

I still don’t understand how lein caused that error, but I guess it’d require more digging into what lein main has changed that may be triggering the spec failure

also good to note that this image lets you get granular with the lein version as well, so even though that’s a dev dependency and running lein run makes my app run fine on 2.9, i updated my cicd to use 2.8.3 for now just to be safe

no worries, just figured i’d raise the alarm here for now. mentioning in #ring as well

thanks @mikerod

✅

@mikerod worth a github issue?

can toss one out there in the next couple days. have to bounce for now, to help the fam

Need a newer version of core.unify - it’s due to using Clojure 1.10

Yeah, I followed the chain of lein-ring -> leinjacker -> core.contracts (0.0.1) ... core.contracts is at 0.0.6 now and depends on core.unify 0.5.7. Given the abandoned status of leinjacker and the inactive status of core.contracts, asking lein-ring to add a dependency on core.unify 0.5.7 seems like the simplest path to a fix.