This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-13
Channels
- # announcements (8)
- # architecture (11)
- # babashka (159)
- # beginners (112)
- # biff (4)
- # chlorine-clover (4)
- # cider (10)
- # clj-kondo (51)
- # cljs-dev (43)
- # cljsrn (10)
- # clojure (45)
- # clojure-bay-area (5)
- # clojure-europe (11)
- # clojure-france (4)
- # clojure-italy (4)
- # clojure-nl (2)
- # clojure-norway (1)
- # clojure-sweden (1)
- # clojure-uk (8)
- # clojurescript (75)
- # code-reviews (1)
- # community-development (2)
- # conjure (88)
- # cryogen (5)
- # data-science (1)
- # datomic (3)
- # dirac (2)
- # fulcro (4)
- # helix (1)
- # jackdaw (5)
- # kaocha (5)
- # leiningen (2)
- # lsp (49)
- # malli (9)
- # mid-cities-meetup (1)
- # off-topic (8)
- # pathom (3)
- # polylith (19)
- # re-frame (6)
- # releases (3)
- # rewrite-clj (1)
- # shadow-cljs (98)
- # spacemacs (2)
- # tools-deps (6)
- # vim (4)
- # xtdb (6)
Is there a flag for a stack trace/debugging? I'm just seeing
λ clj -M:poly help
Don't know how to create ISeq from: clojure.lang.Symbol
λ clj -M:poly info
Don't know how to create ISeq from: clojure.lang.Symbol
@jshaffer2112 I would expect that to either be a problem in your deps.edn
or your workspace.edn
files.
(most likely one or more of your deps.edn
files I suspect)
Can you try clojure -A:dev -Stree
and see if that succeeds? That should validate your top-level deps.edn
file, or at least the :dev
alias in it.
That works fine
What is your :poly
alias?
:poly {:extra-deps {polyfy/polylith
{:git/url ""
:sha "65a7918bb6de886cda7a9b8a5fe7dbdf10996bf8"
:deps/root "projects/poly"}}
:main-opts ["-m" "polylith.clj.core.poly-cli.core"]}
Hmm, that’s the latest issue-66
which is what I’m using.
Is this a public project I can take a look at?
(I’m still betting on a bad deps.edn
file somewhere in the project)
It's not public, but I got a stack trace so I can track it down
:local/root is great
polylith.clj.core.workspace-clj.namespaces-from-disk/import throws on (:import com.opentable.db.postgres.embedded.EmbeddedPostgres)
easy to change the import to []
Looks like it was already fixed in master
Oh, interesting. I tend to forget that Polylith tries to parse code…
It's really weird that it does that even for help
and version
. I thought it had to be deps.edn or workspace.edn too, but I couldn't find anything wrong there
Hopefully, @tengstrand will be updating the issue-66
branch soon and maybe he can merge in that bug fix from master too…
Thanks for taking a look