This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-04-24
Channels
- # beginners (64)
- # calva (40)
- # cider (76)
- # clara (13)
- # clojure (72)
- # clojure-dev (34)
- # clojure-italy (4)
- # clojure-nl (14)
- # clojure-poland (1)
- # clojure-uk (30)
- # clojurescript (58)
- # clr (10)
- # core-async (101)
- # cursive (31)
- # datomic (9)
- # emacs (20)
- # fulcro (2)
- # jackdaw (1)
- # jobs (3)
- # juxt (3)
- # luminus (4)
- # lumo (15)
- # mount (4)
- # nrepl (29)
- # nyc (1)
- # off-topic (27)
- # qlkit (1)
- # quil (5)
- # re-frame (19)
- # reitit (8)
- # remote-jobs (4)
- # rewrite-clj (5)
- # shadow-cljs (45)
- # spacemacs (22)
- # sql (9)
- # uncomplicate (1)
- # xtdb (14)
@kenny https://github.com/cursive-ide/cursive/issues/2162, fixed in the next build.
hello, I was using Cursive, but out of the blue it just stopped recognising the things from Clojure core, I tried refreshing the deps project, but seems like Cursive got lost
everything looking like this
I saw the same issue a while ago, when the clojure version was changed from 1.9 to 1.10 in the git repo. Invalidate and restart did not solve it for me. Had to change the clojure version manually back and forth for cursive to pick it up. (Using lein, in this case)
@wilkerlucio @U0FTV149X @U2FRKM4TW If you have your IntelliJ log and you have a good idea of when this happened, please send the log file indicating roughly when the issue occurred.
@cfleming today I did upgrade intellij again, didnt happened since, but if it does I’ll get the logs
Seeing the issue, again. Traces like these show up in the logs
2019-04-25 15:51:20,782 [ 19866] INFO - il.indexing.FileBasedIndexImpl - Rebuild requested for index ClojureKeywordDefinition
java.lang.Throwable
at com.intellij.util.indexing.FileBasedIndex.requestRebuild(FileBasedIndex.java:70)
at cursive.intentions.resolve$rebuild_all_indexes_BANG_.invoke(resolve.clj:142)
at clojure.lang.Var.invoke(Var.java:383)
at cursive.api.DelayedFn.invoke(DelayedFn.java:36)
at cursive.settings.ClojureProjectResolveSettings$loadState$1.run(ClojureResolveSettings.kt:95)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:311)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
I’ve been experiencing this issue as well. It started today when I upgraded to Cursive v1.8.2-eap1-2019.1
(I’m running IntelliJ 2019.1.1
). I was able to resolve one project by fiddling with the JDK settings, but I have another I was not able to get working. (tried “invalidate and restart”) I see similar stacktraces as above:
2019-04-26 16:36:37,912 [ 15014] INFO - il.indexing.FileBasedIndexImpl - Rebuild requested for index ClojureClasses
java.lang.Throwable
at com.intellij.util.indexing.FileBasedIndex.requestRebuild(FileBasedIndex.java:70)
at cursive.intentions.resolve$rebuild_all_indexes_BANG_.invoke(resolve.clj:142)
at clojure.lang.Var.invoke(Var.java:383)
at cursive.api.DelayedFn.invoke(DelayedFn.java:36)
at cursive.settings.ClojureProjectResolveSettings$loadState$1.run(ClojureResolveSettings.kt:95)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:311)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
@U0DEB9H5W after upgrading IntelliJ to nevermind, I'm on 2019.1.2
I stopped seeing the issue2019.1.1
, confused the version
the clojure setup is correct, my deps.edn
is this for this project:
{:deps {org.clojure/clojure {:mvn/version "1.10.0"}
org.apache.jena/jena-core {:mvn/version "3.10.0"}
org.apache.jena/jena-arq {:mvn/version "3.10.0"}
org.apache.jena/jena-iri {:mvn/version "3.10.0"}
org.apache.jena/jena-tdb {:mvn/version "3.10.0"}}}
it got back working after restarting IntelliJ entirely
@wilkerlucio Which IntelliJ version are you on? Did you just upgrade?
IntelliJ IDEA 2019.1 (Ultimate Edition)
Build #IU-191.6183.87, built on March 27, 2019
JRE: 1.8.0_202-release-1483-b39 x86_64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
macOS 10.14.1
its been some time since I did the update
@wilkerlucio that happened to too, invalidate cache and restart fixed it
in the File
menu
thanks, in my case just a regular restart (without invalidating caches) did the trick
@cfleming the same issue just happened again, I had just that project open (lets call it A), then I opened project B, just after that project A resolution got broken again
and at work I had reports from other coworkers that this is happening with some frequency, not totally sure but seems to started to happen more often after upgrading to IntelliJ 2019
Does anyone know what action is run when a user hits the escape key in the repl? It shifts focus away from the repl editor and back to the last file edited. I’m asking because I’d like to rebind this behavior so that cmd+\ toggles between focusing and hiding the repl editor and so far it only does the former
Looks like it does the Editor -> Escape action, as far as I can see.
@wilkerlucio Someone else mentioned that too, exactly the same symptoms. I think it must be an IntelliJ bug.
I've had the same issue since upgrading to IDEA 2019.1.1 and Cursive 1.8.1. I used the cursive 1.8.1-eap in IDEA 2018.3 without issue. It seems to be nondeterministic - repeatedly loading the same project sometimes fails and sometimes succeeds. I dumped some logs at https://gist.github.com/jffry/228c51978b1f351866a3be98bad5db6d and am happy to help troubleshoot further
I should add that I've experienced this with a variety of projects, some leiningen and some deps, and I have experienced it with both freshly-checked-out repos and projects that have been on my machine for years
@boris834 Unfortunately ESC jumping back to the editor from toolwindows is hard-coded in IntelliJ. There are various IdeaVim issues about this, and various hacks in recent IntelliJ versions, but it’s not very customisable.
I’ve been experiencing this issue as well. It started today when I upgraded to Cursive v1.8.2-eap1-2019.1
(I’m running IntelliJ 2019.1.1
). I was able to resolve one project by fiddling with the JDK settings, but I have another I was not able to get working. (tried “invalidate and restart”) I see similar stacktraces as above:
2019-04-26 16:36:37,912 [ 15014] INFO - il.indexing.FileBasedIndexImpl - Rebuild requested for index ClojureClasses
java.lang.Throwable
at com.intellij.util.indexing.FileBasedIndex.requestRebuild(FileBasedIndex.java:70)
at cursive.intentions.resolve$rebuild_all_indexes_BANG_.invoke(resolve.clj:142)
at clojure.lang.Var.invoke(Var.java:383)
at cursive.api.DelayedFn.invoke(DelayedFn.java:36)
at cursive.settings.ClojureProjectResolveSettings$loadState$1.run(ClojureResolveSettings.kt:95)
at com.intellij.openapi.application.impl.ApplicationImpl$1.run(ApplicationImpl.java:311)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)