Fork me on GitHub
#cider
<
2018-10-16
>
dpsutton00:10:04

ok so i can see the bug. i was able to get a new prompt by just pressing enter, and once i eval'ed something again the spinner calmed down

dpsutton00:10:22

it looks like it just stops the eval immediately but cider isn't aware that it is done

dpsutton00:10:25

@mfiano can you confirm that for me? just press enter. it's not "stuck" it just doesn't know that its no longer doing anything

mfiano00:10:53

Ah yes I can confirm

dpsutton00:10:30

awesome. still a bug. but less buggy

mfiano00:10:53

Ok not as fatal as I thought. I saw the SEVERE at the top, and no prompt, and assumed it was worse than it is

arrdem00:10:59

For all that I’m an absolute CIDER stan, I am seeing inlined deps issues in tools.reader somewhere 😕 falling back to MELPA stable

mfiano05:10:49

Hello. Anyone available to try reproducing an issue before I submit it?

wallydrag05:10:44

Debugger entered--Lisp error: (error "Version must be a string")
  signal(error ("Version must be a string"))
  error("Version must be a string")
  version-to-list(nil)
  version<=("0.18.0" nil)
  cider--check-middleware-compatibility()
  cider--connected-handler()
  run-hooks(nrepl-connected-hook)
  nrepl-start-client-process("127.0.0.1" 8011 nil #f(compiled-function (_) #<bytecode 0x40d48779>))
  cider-nrepl-connect((:project-dir "~/workspace/gojek/allocation-service/" :host "127.0.0.1" :port 8011 :repl-init-function nil :session-name nil :repl-type "clj"))
  cider-connect(nil)
  funcall-interactively(cider-connect nil)
  call-interactively(cider-connect record nil)
  command-execute(cider-connect record)
  helm-M-x(nil "cider-connect")
  funcall-interactively(helm-M-x nil "cider-connect")
  call-interactively(helm-M-x nil nil)
  command-execute(helm-M-x)

wallydrag05:10:22

getting this error when doing cider-connect, i can connect to repl but go-to-defn fails and falls back to gtags and dumb search

wallydrag05:10:59

I am using

spacemacs - 0.200.13
emacs - 26.1
cider - 0.18.0 SNAPSHOT

bozhidar07:10:49

I’ve reverted the cider-nrepl tools.reader dep and pushed a new snapshot.

bozhidar07:10:27

And this time around I’ve even tested that cider-jack-in works normally. 🙂 That being said - I’ve got no idea why the breakage happens.

iagwanderson07:10:39

hi @bozhidar, if I reinstall the package from melpa now, I’ll already get the rollbacked version?

iagwanderson07:10:49

I still get that error from cider-jack-in

arrdem07:10:18

Thanks Bozhidar!

bozhidar07:10:30

The bug was not in the MELPA package, but in the cider-nrepl itself.

bozhidar07:10:09

You should delete cider-nrepl-0.19-SNAPSHOT locally for .m2 to force it to be refetched.

bozhidar07:10:33

@wallydrag How did start the nREPL server you’re connecting to?

wallydrag08:10:59

i have an nrepl server in the my code which i run on terminal and then connect to that port

bozhidar07:10:40

(seems you don’t cider-nrepl loaded and that we forgot to add a nil check in the version comparison)

dominicm07:10:58

Don't you check the describe output first to see if cider-version is supported?

dominicm07:10:33

(Not that I do this, but I figured cider would do this implicitly)

iagwanderson07:10:22

works fine now @bozhidar

bozhidar07:10:17

@dominicm We do, but afterwards there’s some version parsing code that used to be nil safe, but I guess now it’s not. 🙂

dominicm07:10:51

@bozhidar so that would mean that cider must be loaded, no?

iagwanderson07:10:36

when I evaluate cider-eval-last-sexp in any function it works fine, but if I try that in the namespace definition I receive this message error in process filter: Wrong type argument: characterp, nil

bozhidar07:10:39

@iagwanderson Some stacktrace would be useful here.

bozhidar07:10:51

> @bozhidar so that would mean that cider must be loaded, no?

iagwanderson07:10:04

@bozhidar I’m trying to figure it out how to get a proper stacktrace because there is nothing in the cider-repl

iagwanderson07:10:48

emacs -Q for the rescue. something I configured break it. o/ one more dawn in the dungeons

bozhidar07:10:16

@dominicm Well, it means that nREPL is loaded and then you start going the describe keys and check what’s there, which is where this code breaks. You can’t really get a nil version if cider-nrepl is loaded.

dominicm07:10:49

@bozhidar the code isn't nil safe around checking whether the cider-version op is present, you mean? That makes more sense.

bozhidar08:10:51

Yep. I guess I broke this when I changed a check from “is there some version” to “is the version higher than some required version”. Weird mistake if I did it, but completely plausible given the stacktrace.

bozhidar08:10:41

As for tools.reader and tools.namespace - see https://dev.clojure.org/jira/browse/TRDR-55 Seems that’s some bug in tools.namespace, which I assume no one is going to fix any time soon.

dromar5608:10:52

Hello, a question about packages: for CIDER and other related clojure packages, is it better to be on melpa-stable or melpa?

manuel09:10:36

@dromar56 I've always been on MELPA, and the CIDER team is pretty quick at bug-fixing whenever I find a problem 🙂

manuel09:10:53

TBH, I don't think I've ever used melpa-stable in my Emacs-life.