Fork me on GitHub
#cider
<
2019-02-14
>
vigilancetech00:02:49

yes, and on a whole different OS/installation. Same thing

dpsutton00:02:09

are you still getting the warning about nrepl 19?

vigilancetech00:02:27

can't get that far

vigilancetech00:02:42

connection fails from cider-connect-cljs

dpsutton03:02:10

When it says this, how are you specifying the cider nrepl version?I haven't had to specify a version ever. Certainly not since v12

dpsutton05:02:20

@vigilancetech i'm removing all references to cider-nrepl from the project and letting my version of CIDER set itself up. On both linux and fedora i'm able to start both client and electron builds. I'm not sure what issue you are having but i would probably look at reinstalling things at this point?

vigilancetech05:02:59

@dpsutton if I take that out I get: helm-M-x: ‘cider-connect-cljs’ requires the nREPL op "classpath" (provided by cider-nrepl)

dpsutton05:02:00

[nREPL] Starting server via /usr/local/bin/npx shadow-cljs -d nrepl:0.6.0 -d cider/piggieback:0.4.0 -d cider/cider-nrepl:0.21.0 server this is what my invocation looks like. can you see what CIDER is doing to crank up the project?

dpsutton05:02:48

it is in the *Messages* buffer. (if you're not familiar. the experience levels are sometimes absolute beginner and sometimes emacs guru so its hard to talk on the right level at first :)

vigilancetech05:02:04

that's what was in my messages buffer

dpsutton05:02:07

so its complaining about the caught middleware which was added recently in 0.6.0

vigilancetech05:02:13

and no cider buffer was created

dpsutton05:02:22

nrepl:0.6.0?

dpsutton05:02:09

maybe delete ~/.m2/repository/cider?

vigilancetech05:02:12

I have no nrepl dep any more in the

vigilancetech05:02:28

in the shadow-cljs.edn file

dpsutton05:02:43

that's fine. but the command that CIDER uses includes -d nrepl:0.6.0?

dpsutton05:02:00

cider-nrepl needs it. CIDER takes care to inject piggieback, nrepl, and cider-nrepl for you

dpsutton05:02:09

just making sure those values are all mutually compatible

vigilancetech05:02:15

okay, this is really strange. I'm not finding .m2/ anywhere. I'm on msys2

dpsutton05:02:35

ah. i have no idea what's going on there then

dpsutton05:02:56

is it true that your startup command matches the one i put above? exactly?

vigilancetech05:02:58

yeah, gonna take me a few mins to figure out where this cache is

dpsutton05:02:18

no worries. just making sure it is definitely the OS weirdness and not anything trivial before we jump into that

vigilancetech05:02:43

I can't find that command in messages or anything like it. I'm using cider-connect-cljs not any kind of jack-in

dpsutton05:02:58

what are you using to start the server then

vigilancetech05:02:02

I've never had any luck with jack in

dpsutton05:02:07

how do you start up shadow?

vigilancetech05:02:15

I just do shadow-cljs watch electron client

dpsutton05:02:30

ah ok. you need nrepl in there

dpsutton05:02:36

note how cider does it

dpsutton05:02:51

/usr/local/bin/npx shadow-cljs -d nrepl:0.6.0 -d cider/piggieback:0.4.0 -d cider/cider-nrepl:0.21.0 server

vigilancetech05:02:08

so I need to add those -d deps on my command line?

dpsutton05:02:22

those deps need to be there: piggieback, nrepl and cider-nrepl. CIDER does it automatically for you. if you want to start it yourself make sure those are there

dpsutton05:02:34

and if you do that i'm hopeful that all your problems will evaporate

vigilancetech05:02:50

can't they be put in shadow-cljs.edn?

dpsutton05:02:54

they sure can

dpsutton05:02:24

at the risk of adding more deps that non-cider users will have. if that's fine go for it.

dpsutton05:02:37

but i guess in a cljs project who cares what jvm artifacts are lying around

dpsutton05:02:58

i'm sorry. i thought you were using cider-jack-in-cljs this whole time. i apologize

vigilancetech05:02:59

yeah, I'm going to run the production version thru the closure compiler anyway

vigilancetech05:02:30

yeah, no I mentioned it above. I've never been able to get any jack-in to work at all. Not sure why

dpsutton05:02:11

not sure. my guess would be your many OSes under one roof situation going on. you're doing cygwin stuff is that right?

dpsutton05:02:30

anyways sorry to waste your time. if you throw those deps in there it should startup just fine

vigilancetech05:02:47

not really. I have a c# server that has to run under windows so I'm using msys to develop a hoplon front in for it on.

vigilancetech05:02:14

Just so I don't have to have two machines running at the same time (or some kind of VM)

vigilancetech05:02:31

but, initially at least, its going to be an electron app

dpsutton05:02:41

i enjoyed my C# years. yeah that makes sense. and windows apps do not make it easy to just throw them on a box or a virtualized thing

vigilancetech05:02:13

Well, fortunately I didn't write the c# and I don't plan on touching it (I got someone else for that).

vigilancetech05:02:54

I will say I'm kind of having fun and being amazed how much msys2 tricks me into thinking I'm developing in a Unix environment. If you get it set up just right that is.

vigilancetech05:02:08

next time I might try WSL but this just came together quicker

vigilancetech05:02:29

@dpsutton that seems to have fixed it somewhat, but I'm getting this:

WARNING: No Clojure project was detected. The
refactor-nrepl middleware was not enabled. 

vigilancetech05:02:45

(I turned that refactor-nrepl dep back on)

dpsutton05:02:46

Not sure how cljs compatible refactor is and perhaps it doesn't "speak" shadow. I have no idea

vigilancetech05:02:04

ok, thanks for all your help!

dpsutton05:02:17

I suppose it's looking for a boot or lein or deps project file

dpsutton05:02:22

But I don't know

vigilancetech05:02:19

yeah, gotcha. Considering there's a variable to suppress the message, I guess its one of those "YMMV w/cljs" packages.

manuel09:02:31

just FYI, I found this with latest cider-nrepl and shadow-cljs: https://github.com/clojure-emacs/cider-nrepl/issues/596

manuel09:02:00

Fixed with shadow-cljs 2.7.34.