Fork me on GitHub
#cursive
<
2022-03-03
>
Edmund06:03:01

Hi all. I decided to give cursive a shot on Windows. Installed the plugin and followed the getting started guide but right out of the box it gives the below error. What could I be missing. I can't seem to find anything on this anywhere. java.lang.RuntimeException: Could not create shim at cursive.shim.ShimProvider.getShim(Shim.kt:148) at cursive.shim.ShimProvider.withShim(Shim.kt:115) at cursive.deps.DepsProjectDetails.doGetDetails(Project.kt:176) at cursive.deps.DepsProjectDetails.doGetDetails(Project.kt:87) at cursive.build.BuildSystemProjectDetails.getProjectDetails(BuildSystem.kt:45) at cursive.build.BuildSystemProjectsManager.reimportAllProjects$lambda-3$lambda-2(BuildSystemManager.kt:149) at cursive.build.BuildSystemUtil$runTask$1$1.run(BuildSystemUtil.kt:83) at com.intellij.openapi.progress.impl.CoreProgressManager.startTask(CoreProgressManager.java:436) at com.intellij.openapi.progress.impl.ProgressManagerImpl.startTask(ProgressManagerImpl.java:120) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcessWithProgressAsync$5(CoreProgressManager.java:496) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$3(ProgressRunner.java:244) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$runProcess$2(CoreProgressManager.java:188) at com.intellij.openapi.progress.impl.CoreProgressManager.lambda$executeProcessUnderProgress$12(CoreProgressManager.java:624) at com.intellij.openapi.progress.impl.CoreProgressManager.registerIndicatorAndRun(CoreProgressManager.java:698) at com.intellij.openapi.progress.impl.CoreProgressManager.computeUnderProgress(CoreProgressManager.java:646) at com.intellij.openapi.progress.impl.CoreProgressManager.executeProcessUnderProgress(CoreProgressManager.java:623) at com.intellij.openapi.progress.impl.ProgressManagerImpl.executeProcessUnderProgress(ProgressManagerImpl.java:66) at com.intellij.openapi.progress.impl.CoreProgressManager.runProcess(CoreProgressManager.java:175) at com.intellij.openapi.progress.impl.ProgressRunner.lambda$submit$4(ProgressRunner.java:244) 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:829) Caused by: java.lang.RuntimeException: Unable to resolve symbol: requiring-resolve in this context, compiling:(clojure/tools/deps/alpha/util/s3_transporter.clj:27:22) at clojure.lang.Compiler.analyze(Compiler.java:6792) at clojure.lang.Compiler.analyze(Compiler.java:6729) ...

☝️ 1
cfleming06:03:11

Hi Edmund, this is a bug which is fixed in the current EAP (beta) series, the fix hasn’t made its way into a stable build yet. If you don’t mind switching to the EAP builds, you can follow the instructions here: https://cursive-ide.com/userguide/#choosing-to-receive-eap-beta-builds

Edmund06:03:14

Hi @U0567Q30W. Thanks a lot 🙏

Edmund12:03:36

Still getting the same issue on the latest EAP versions. Also tried old versions and still got the same issue. Could there be some setting somewhere I'm missing?

steffan17:03:25

If your project uses deps.edn and you are using the option Settings > Build, Execution, Deployment > Build Tools > Clojure Deps > Use tools.deps directly (as you are seemingly forced to on Windows, as I can't for the life of me figure out the correct Path to clojure command setting for the Use CLI tools option) then I may have the answer for you as I ran into this myself. There was a very recent bugfix in tools.deps which you can pick up by clicking the Refresh button, then selecting the latest (`0.12.1153`), then clicking Download

Edmund19:03:29

I already have that setting and its on the latest version of tools.deps.

cfleming20:03:00

@UR7H0UC0M Sorry, there’s an extra step required, detailed in the release notes of the EAP fixing the bug: https://groups.google.com/g/cursive/c/O_oettEjv40/m/agRLYvdBCAAJ

cfleming20:03:58

Apologies for not mentioning it earlier.