Fork me on GitHub
Slack Archive

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

2020-05-07

Channels

#cursive
<
2020-05-07
>
nmkip01:05:24

Do you use test.check with cursive?

royalaid04:05:55

@cfleming have you seen "Error handling response - class java.lang.IllegalArgumentException: No matching clause: :state" anywhere?

cfleming04:05:36

Are you seeing that coming out of Cursive somewhere?

royalaid04:05:59

is the project I am running

cfleming04:05:13

When are you seeing it?

royalaid04:05:14

and I connect up my repl

royalaid04:05:10

I have never seen this from the project before

royalaid04:05:16

and I have run it before via cursive

cfleming04:05:27

Yeah, that’s coming from Cursive. Which version are you on?

royalaid04:05:50

1.9.2.-eap2-2020.1

royalaid04:05:58

strangely the repl works fine

cfleming04:05:00

Yes, I think I see the problem. That was introduced in the latest EAP fixing https://github.com/cursive-ide/cursive/issues/2100

royalaid04:05:16

Repro is pretty easy

royalaid04:05:59

thanks for the quick response as always

cfleming05:05:40

No worries - so you basically clone that project, and then connect a remote REPL to 8777?

cfleming05:05:11

@U0S3YK6HK I’ve started that project and connected to the REPL, is there anything in particular you have to do to provoke the problem?

cfleming05:05:55

Looking at your screenshot above looks like not, but I can eval (+ 1 2) with no problem.

cfleming05:05:49

I basically cloned, imported the project, ran npm install then npm run watch, waited for a while then connected the REPL. Did I miss a step there?

royalaid05:05:44

no I don't think so

royalaid05:05:51

Let me "reclone"

royalaid05:05:02

and try it fresh again

royalaid05:05:49

Connecting remote repl on port 8777?

royalaid05:05:32

I am using yarn

royalaid05:05:38

but again in the past that hasn't been a problem

cfleming05:05:59

I doubt it, this is an nREPL thing.

cfleming05:05:34

Basically, nREPL sends back a :status field, and I changed how I handled that in the latest EAP. The previous version had a bug, but I realised that I no longer handle the default case, which is where that error comes from. I’m pretty sure I can fix that but I can’t easily test it if I can’t repro it. But I can make the fix, and then after the next EAP just let me know if it’s fixed.

cfleming05:05:42

Are you using any nREPL middleware in your user profiles?

cfleming05:05:06

I guess not, since this isn’t lein. Any others in your .nrepl.edn file?

cfleming05:05:16

Or whatever that thing is called

royalaid05:05:47

project title to confirm this is the new one

royalaid05:05:13

checking .edn thing now

cfleming05:05:24

Yeah, that looks like it to me.

royalaid05:05:15

so I have a .shadow-cljs

royalaid05:05:22

and that has cider-snapshots

royalaid05:05:31

moving it and gonna try again

cfleming05:05:34

Might be ~/.nrepl/nrepl.edn?

cfleming05:05:58

Or in a .nrepl.edn file in the project.

cfleming05:05:10

CIDER was the problem all along 🙂

royalaid05:05:43

completely forgot this was even a thing

royalaid05:05:47

:face_palm:

royalaid05:05:54

ty as always

cfleming05:05:56

Still, it’s still a Cursive bug

cfleming05:05:11

Can you paste that here and I’ll use it to repro?

royalaid05:05:23

{:dependencies
 [[cider/cider-nrepl "0.23.0-SNAPSHOT"]
  [refactor-nrepl "2.5.0-SNAPSHOT"]]}

royalaid05:05:37

hopefully that triggers it for you 😬

cfleming05:05:53

CIDER always triggers me

😂 4
cfleming05:05:06

That was it. I had to add the deps manually to the project, for some reason.

cfleming05:05:06

Ok, fixed, thanks!

royalaid05:05:22

Glad to help! Thanks for the quick turnaround

Joshua Ewulo16:05:26

Dear all, I am new to Clojure. I am using Cursive on IntelliJ. I can Build my project but when I try to run it I get this error. Error running 'test (1)': failed to access class com.intellij.execution.impl.ProcessStreamsSynchronizer from class com.intellij.execution.impl.ConsoleViewRunningState (com.intellij.execution.impl.ProcessStreamsSynchronizer is in unnamed module of loader com.intellij.util.lang.UrlClassLoader @7f9a81e8; com.intellij.execution.impl.ConsoleViewRunningState is in unnamed module of loader http://com.intellij.ide.plugins.cl.PluginClassLoader @7b0d6c9c). Does anybody understand what I am doing wrong?

thumbnail19:05:05

A coworker hit the exact same issue today, IIRC he deleted the .idea/-folder in the project he was working in, reimport and stuff started working properly

dazld17:05:21

is adding a dependency to deps edn broken atm? IntelliJ ultimate, 2020.1, cursive 1.9.2-eap2-2020.1

dazld17:05:40

have done the usual invalidate cache dance

cfleming23:05:07

I’m not sure, I’ll check that.

salam20:05:41

it appears that the abbreviation and the description in the live template for clojure.test/is got swapped up.

salam20:05:54

as part of this fix, it would be very helpful to rename first to expected and second to actual as people often get confused by which goes where when they switching among different test libraries.

cfleming23:05:07

True, although I think I deliberately didn’t do that in this case because clojure.test doesn’t distinguish between them.

salam00:05:44

ah, you're right. i just dived into the code and realized that clojure.test has very different definitions for expected and actual.