Clojurians Log v2
polylith
experiencing a pretty opaque error/stack-trace when trying to start up clojure -M:poly in my workspace; its been a few weeks since I've created a new component/base and so haven't run it in a while, and so can't pin down the error to a specific bit of code easily. My dev-file (which imports a significant amount of namespaces) runs without any errors/exceptions, so there's no namespace thats clearly broken afaict: stack-trace in 🧵
ST in file:
based on the trace, it seems like its breaking on a "sort-libs" step?
I'll send the deps.edn as well, if its related
I suspect the most likely issue is a deps.edn in one of your bases or components that has an unparseable :mvn/version?
thats what im trying to look through now yea, not sure what it'd be though, I've seen a combination of version schemes that haven't had issue (ive had 1.12.0-alpha9_4 for a while without issue i believe, which is the most esoteric looking version scheme that I can see)
let me see if i can get a dump of versions with some grep magic
versions:
not seeing anything super weird here? i have commented out the 1.12.0-alpha9_4 dependency and it didnt seem to do anything
What happened that produced {metosin/reitit {:mvn/version "0.7.0-alpha7"} as opposed to the rest all starting with {:mvn/version?
i missed a manual dt{ (delete) when editing the file :^)
All I can suggest at this point is commenting out parts of :dev > :extra-deps to bisect until you find the likely candidate...
yea... gloves on~
okay.. it looks like i had a couple libs that had different versions in the :dev alias and individual project/component deps, and that was the cause of this 'sorting error' stacktrace, very interesting...
i appreciate the prodding
What were the different versions that couldn't be "sorted" by Polylith?
0.7.0 vs 0.7.0-alpha7 for one of them (reitit, serendipitously), and 2.8.0 vs 2.8.0-beta3 (http-kit); so it seems like it doesn't like a mixture of flat-versions and versions with qualifiers
That sounds like a bug in Polylith -- you could create a GH issue... it would probably be fairly easy to create a minimal repro with that information known...
I'm glad it's not the deps.edn typo problem. Still, deps could do a better job checking the keys. I once spent a good amount of time trying to figure out why nothing was working. I had :extra-path key (singular, proper is :paths) in one of the deps.edn files. I wish something had told me about it.
Polylith doesn't really use tools.deps for a lot of this -- which is why you get bugs like these. tools.deps can compare these versions just fine.