This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-09-09
Channels
- # announcements (5)
- # beginners (53)
- # clj-kondo (4)
- # cljdoc (3)
- # cljs-dev (11)
- # cljsjs (1)
- # clojure (59)
- # clojure-europe (15)
- # clojure-italy (6)
- # clojure-nl (9)
- # clojure-spec (22)
- # clojure-uk (26)
- # clojurescript (16)
- # clojutre (6)
- # cursive (27)
- # datomic (34)
- # duct (1)
- # figwheel-main (2)
- # fulcro (12)
- # graphql (14)
- # jackdaw (9)
- # jobs (1)
- # kaocha (4)
- # luminus (1)
- # off-topic (11)
- # pathom (1)
- # pedestal (2)
- # re-frame (6)
- # reagent (10)
- # ring-swagger (34)
- # shadow-cljs (47)
- # spacemacs (21)
- # sql (3)
- # tools-deps (37)
- # uncomplicate (11)
- # vim (17)
ah i figured it out, it was disabled in the preferences
i didn’t know it was something you could turn off, and downgrading my intelliJ disabled it
PSA: there’s a new dev build out of the updated deps integration, if you’re using the first one check it out here: https://groups.google.com/d/msg/cursive/D4yCqNC6iiM/Bc4-EKbaAQAJ
I have been getting this message fairly often when using the dev build. I don't remember getting it before switching to the dev build so this may be a regression.
Sometimes that happens if you accidentally have classes on classpath twice..e.g. if you’ve built an uberjar to target
and the classes in there end up on classpath.
Pretty sure nothing has changed in these projects besides updating to the Cursive dev build.
If you do Navigate | Namespace… and search for clojure.test.check
or clojure.test.check.clojure-test
, do you see multiple copies of either of them?
It’s possible that the new integration has some differences around how it handles excluded folders.
That’s probably the reason for the spurious dependency cycle error. I’ll add some code that logs some debug information when cycles happen so we get a clearer idea of what’s going on.
Yes - go to Help | Debug log settings…, then add #cursive.repl.actions
to the box there. Then reproduce, and check your log. You should see some debug log at the end showing the dependency cycle and the files which those namespaces are found in.
You should see something like this:
2019-09-20 10:32:24,984 [ 74368] DEBUG - #cursive.repl.actions - Namespace cycle: clj:dependency-loop-log.core (/Users/colin/dev/cursive-bugs/dependency-loop-log/src/dependency_loop_log/core.clj) -> clj:dependency-loop-log.core2 (/Users/colin/dev/cursive-bugs/dependency-loop-log/src/dependency_loop_log/core2.clj) -> clj:dependency-loop-log.core (/Users/colin/dev/cursive-bugs/dependency-loop-log/src/dependency_loop_log/core.clj)
Oh, actually - don’t think you’re getting that message when I thought you were. When is that occurring?
Right, I see. I’ll add the log in that case too - that error usually appears when trying to load a file in the REPL. One thing you could try is opening the clojure.test.check
namespace and trying to load it into your REPL. That should show the current log.