This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-12
Channels
- # adventofcode (6)
- # beginners (148)
- # boot (5)
- # calva (1)
- # cider (10)
- # cljdoc (10)
- # cljs-dev (8)
- # cljsrn (10)
- # clojure (180)
- # clojure-dev (24)
- # clojure-europe (2)
- # clojure-finland (1)
- # clojure-italy (32)
- # clojure-losangeles (1)
- # clojure-nl (40)
- # clojure-spec (10)
- # clojure-uk (44)
- # clojured (4)
- # clojurescript (88)
- # community-development (33)
- # core-async (7)
- # cursive (19)
- # datomic (98)
- # duct (3)
- # events (1)
- # figwheel-main (10)
- # fulcro (62)
- # leiningen (23)
- # luminus (18)
- # off-topic (19)
- # pedestal (6)
- # re-frame (46)
- # reagent (21)
- # ring (17)
- # ring-swagger (3)
- # shadow-cljs (94)
- # slack-help (9)
- # spacemacs (14)
- # sql (1)
- # testing (4)
- # tools-deps (14)
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.
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
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.