This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-10-16
Channels
- # 100-days-of-code (1)
- # announcements (1)
- # beginners (93)
- # boot (46)
- # cider (40)
- # cljdoc (4)
- # cljs-dev (7)
- # clojure (78)
- # clojure-conj (12)
- # clojure-dev (17)
- # clojure-italy (5)
- # clojure-nl (10)
- # clojure-spec (34)
- # clojure-uk (36)
- # clojurescript (56)
- # code-reviews (6)
- # core-async (31)
- # cursive (12)
- # datascript (9)
- # datomic (19)
- # devops (2)
- # editors (3)
- # emacs (6)
- # events (2)
- # figwheel (1)
- # figwheel-main (11)
- # fulcro (59)
- # graphql (10)
- # hyperfiddle (3)
- # keechma (5)
- # leiningen (26)
- # luminus (1)
- # nrepl (5)
- # re-frame (5)
- # reitit (10)
- # shadow-cljs (64)
- # spacemacs (29)
- # tools-deps (6)
- # uncomplicate (8)
- # vim (2)
- # yada (4)
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
it looks like it just stops the eval immediately but cider isn't aware that it is done
@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
Ah yes I can confirm
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
For all that I’m an absolute CIDER stan, I am seeing inlined deps issues in tools.reader somewhere 😕 falling back to MELPA stable
Hello. Anyone available to try reproducing an issue before I submit it?
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)
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
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.
hi @bozhidar, if I reinstall the package from melpa now, I’ll already get the rollbacked version?
You should delete cider-nrepl-0.19-SNAPSHOT
locally for .m2
to force it to be refetched.
@wallydrag How did start the nREPL server you’re connecting to?
i have an nrepl server in the my code which i run on terminal and then connect to that port
i also came across this chat https://clojurians-log.clojureverse.org/cider/2018-08-15
(seems you don’t cider-nrepl
loaded and that we forgot to add a nil check in the version comparison)
@dominicm We do, but afterwards there’s some version parsing code that used to be nil safe, but I guess now it’s not. 🙂
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
@iagwanderson Some stacktrace would be useful here.
@bozhidar I’m trying to figure it out how to get a proper stacktrace because there is nothing in the cider-repl
emacs -Q
for the rescue. something I configured break it. o/ one more dawn in the dungeons
@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.
@bozhidar the code isn't nil safe around checking whether the cider-version
op is present, you mean? That makes more sense.
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.
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.
i have an nrepl server in the my code which i run on terminal and then connect to that port
Hello, a question about packages: for CIDER and other related clojure packages, is it better to be on melpa-stable or melpa?