This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-22
Channels
- # announcements (10)
- # babashka (40)
- # beginners (192)
- # calva (9)
- # cider (2)
- # clj-kondo (9)
- # clojure (69)
- # clojure-dev (15)
- # clojure-europe (29)
- # clojure-gamedev (6)
- # clojure-italy (2)
- # clojure-nl (41)
- # clojure-spec (49)
- # clojure-uk (11)
- # clojurescript (68)
- # conjure (1)
- # cryogen (20)
- # cursive (37)
- # data-oriented-programming (10)
- # data-science (4)
- # datahike (7)
- # datomic (8)
- # depstar (14)
- # emacs (7)
- # events (2)
- # figwheel-main (1)
- # fulcro (81)
- # honeysql (22)
- # hugsql (5)
- # juxt (3)
- # leiningen (8)
- # lsp (314)
- # malli (20)
- # meander (15)
- # membrane (20)
- # mid-cities-meetup (11)
- # practicalli (2)
- # reagent (2)
- # remote-jobs (2)
- # ring-swagger (1)
- # rum (3)
- # sci (21)
- # shadow-cljs (52)
- # startup-in-a-month (1)
- # testing (9)
- # tools-deps (41)
- # vim (8)
- # xtdb (4)
Hi folks! How do you prevent mixing up clj and clojurescript repls and sending code (especially from .cljc files) to the wrong ones, any tips? @cfleming would it be perhaps possible to have different color backgrounds for clj x cljs repl? I know the name of the repl is written above it but I needed it rarely and thus normally just ignore it so it is impossible to spot that I am in the "wrong" repl.
I have a Dygma Raise macro for switching repl, i.e. one hotkey in my Dygma Raise keyboard.
Thank you! Though my problem is not switching but noticing which repl I am in
Aah, ok. I use names like "backend" and "frontend" for different repls, but still occasionally send e.g. Clojure code to frontend (Clojurescript) repl. I have the macro hotkey to quickly switch to the right repl.
Well. I’m completely borked this morning and can’t figure out why, or how to fix it. All my Clojure projects are blowing up and losing their deps files. I had enabled Kondo earlier so suspect that has something to do with it, but I’ve disabled and I’m still crapping out with this exception:
Error resolving /Users/rporter/projects/ridehealth/services/ridehealth.fltmatch/deps.edn:
java.lang.NullPointerException
at cursive.deps.relocate$with_deps_relocation.invokeStatic(relocate.clj:35)
at cursive.deps.relocate$with_deps_relocation.invoke(relocate.clj:31)
at cursive.deps.relocate$with_relocation.invokeStatic(relocate.clj:57)
at cursive.deps.relocate$with_relocation.invoke(relocate.clj:43)
at cursive.deps.project$project_details$fn__1234.invoke(project.clj:153)
at clojure.core.protocols$fn__8183.invokeStatic(protocols.clj:168)
at clojure.core.protocols$fn__8183.invoke(protocols.clj:124)
at clojure.core.protocols$fn__8138$G__8133__8147.invoke(protocols.clj:19)
at clojure.core.protocols$seq_reduce.invokeStatic(protocols.clj:31)
at clojure.core.protocols$fn__8170.invokeStatic(protocols.clj:75)
at clojure.core.protocols$fn__8170.invoke(protocols.clj:75)
at clojure.core.protocols$fn__8112$G__8107__8125.invoke(protocols.clj:13)
at clojure.core$reduce.invokeStatic(core.clj:6833)
at clojure.core$reduce.invoke(core.clj:6815)
at cursive.deps.project$project_details.invokeStatic(project.clj:129)
at cursive.deps.project$project_details.invoke(project.clj:76)
at clojure.lang.Var.invoke(Var.java:388)
at org.projectodd.shimdandy.impl.ClojureRuntimeShimImpl.invoke(ClojureRuntimeShimImpl.java:124)
at org.projectodd.shimdandy.impl.ClojureRuntimeShimImpl.invoke(ClojureRuntimeShimImpl.java:117)
at cursive.shim.ShimBootstrap$Shim.apply(ShimBootstrap.java:53)
at cursive.deps.DepsProjectDetails$doGetDetails$details$1.invoke(Project.kt:162)
at cursive.deps.DepsProjectDetails$doGetDetails$details$1.invoke(Project.kt:84)
at cursive.shim.ShimProvider.withShim(Shim.kt:110)
at cursive.deps.DepsProjectDetails.doGetDetails(Project.kt:161)
at cursive.deps.DepsProjectDetails.doGetDetails(Project.kt:84)
at cursive.build.BuildSystemProjectDetails.getProjectDetails(BuildSystem.kt:42)
at cursive.build.BuildSystemProjectsManager$reimportAllProjects$$inlined$synchronized$lambda$1.run(BuildSystemManager.kt:148)
at cursive.build.BuildSystemUtil$runTask$1$1.run(BuildSystemUtil.kt:93)
at com.intellij.openapi.progress.impl.CoreProgressManager$TaskRunnable.run(CoreProgressManager.java:962)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:472)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:235)
at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:178)
at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:658)
at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:610)
at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:65)
at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:165)
at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:235)
at java.base/java.util.concurrent.CompletableFuture$AsyncSupply.run(CompletableFuture.java:1700)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:668)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1$1.run(Executors.java:665)
at java.base/java.security.AccessController.doPrivileged(Native Method)
at java.base/java.util.concurrent.Executors$PrivilegedThreadFactory$1.run(Executors.java:665)
at java.base/java.lang.Thread.run(Thread.java:834)
I'm not sure what clj-kondo would have to do with this, since it doesn't do anything with deps.edn
I don’t think it did. It was just the only change I had made.
I’ve tried other projects that haven’t been touched recently and get the same error.
I used to find if everything suddenly stopped working it was because snap updated my intellij (I have since stopped using snap)
I’m still on 2020.3.2.
I’ve been an IJ user for 20 years and a Cursive user for about two. But right now, I’m super close to throwing it in the trash and re-learning emacs.
Ah. Wait…I may have made one other update external to IJ.
brew upgraded clj. >_<
Hi @coyotesqrl - you’ve probably already figured this out but there appears to be a problem with Cursive and clojure 1.10.2.790 : https://github.com/cursive-ide/cursive/issues/2511
Yep. Once I realized Clojure had updated, I remembered seeing that post the other day. Thanks!
I just came to check to see if this had been reported. Was wondering what was going on. I resolved it temporarily by downgrading to previous version until the fix is released. 😃
I ran into this myself yesterday evening but solved the problem by downgrading clojure with clojure homebrew tap: https://clojure.org/news/2020/02/28/clojure-tap
Yes, sorry about that issue, I reproduced it yesterday and hopefully will be releasing a fix today.
is it something I broke?
I know, just wondering what it was
Ahhh. They were actually duplicates and I did some cleanup. I did do some looking to see if anyone would be affected but can’t see yours of course. Sorry about that...
No worries. I’m checking to see if I can run some sanity check tests when you check something in to deps, but it’s looking tricky.
I’m not even sure why I was using as-canonical since I used canonicalize in a different spot to check for the functionality being present.
these releases are typically available for at least a few days as prereleases before I officially release - I usually announce those on #tools-deps and #releases
tracking that would probably at least give you a heads up
you could programmatically track it by watching https://github.com/clojure/homebrew-tools/tree/master/Formula or https://github.com/clojure/brew-install/blob/1.10.2/devel.properties
Ok, thanks - I’m trying to figure this out at the moment. So everything that’s under releases at Github is an official release, correct?
I'm going to add back in that as-canonical method (undoc'ed) to cut down on version mismatch failures
so if you're going to pick one, I'd pick that one https://clojure.org/releases/tools