anyone experienced cider hanging on bigdecimal values in test expected/actual reports?

Uncaught exception in thread nREPL-worker-3:
                                          java.lang.Thread.run              Thread.java:  745
            java.util.concurrent.ThreadPoolExecutor$Worker.run  ThreadPoolExecutor.java:  617
             java.util.concurrent.ThreadPoolExecutor.runWorker  ThreadPoolExecutor.java: 1142
                                                           ...                               
 clojure.tools.nrepl.middleware.interruptible-eval/run-next/fn   interruptible_eval.clj:  190
                    cider.nrepl.middleware.test/handle-test/fn                 test.clj:  215
                                                           ...                               
                                   clojure.core/with-bindings*                 core.clj: 1963 (repeats 2)
                                            clojure.core/apply                 core.clj:  657
                                                           ...                               
                 cider.nrepl.middleware.test/handle-test/fn/fn                 test.clj:  220
                clojure.tools.nrepl.transport.FnTransport/send            transport.clj:   28
                      clojure.tools.nrepl.transport/bencode/fn            transport.clj:  103
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21139/fn              bencode.clj:  382
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21149/fn              bencode.clj:  398
                                                           ...                               
                      clojure.tools.nrepl.bencode/eval21114/fn              bencode.clj:  326
 java.lang.IllegalArgumentException: Cannot write value of type class java.math.BigDecimal

Hi, newbie here, please excuse my ignorant questions... Today I'm attempting to use the cider debugger for the first time. Is this the right place to ask, or is there a different channel that I should go to?

Here is my question. When I place point on a top level form in my .clj file, hit C-u C-M-x and expect to be dropped into a debug session. Instead I get the message <C-s-268632088> is undefined. Any pointers?

Hm. Also cider-auto-test-mode is not defined.

Still really missing some basics here.

If someone can point me how to start debugging this that would be cool. I'll be here for another 6 hours or so at least 🙂

Well... some progress? Now C-u C-M-x evaluates the top level form and inserts the value at the point. Not a debugger, but something different at least.

@vinal I haven't used the cider debugger much but you need to run your app from the cider nrepl session or use cider-connect to connect the cider nrepl session to the running app and then when your fn gets executed it will stop on the instrumented fn like a breakpoint was set and you get a number of options to inspect locals, step through code etc.

I've just upgraded to cider 0.14.0 from 0.12.x and I'm getting the classic CIDER's version (0.14.0) does not match cider-nrepl's version (nil). Things will break! warning. I've checked and the project.clj doesn't have cider-nrepl specified, neither does ~/.lein/profiles.clj, cider-inject-dependencies-at-jack-in is set to t and I can see the message with the update-in adding the 0.14.0 version of cider-nrepl when I cider-jack-in. I've also tried manually adding the 0.14.0 version of cider-nrepl into the project.clj and still get the warning. Basically, I've exhausted everything in the troubleshooting page, any ideas?

i’ve seen a msg lately on gitter saying the same but stating that everything still works as expected

so you might want to test if M-. actually works @agile_geek

Must admit I haven't noticed anything breaking yet

yup, might be just a glitch in the version checking logic...

Must be... but bit distracting

Thanks @benedek

np

Have to catch up sometime

deffo

@agile_geek Thanks for the heads up. Just noticed I'm on cider 0.8.1 - I'll upgrade and try to debug again.

@vinal not even sure cider debug was a feature of 0.8.1 I think it came in around 0.10.x?

but that's from memory

I think I just installed the default with package-install at the time...

Hmm, I only see the versions 20141120.1746 (installed), 0.8.2 (marmalade) in list-packages.

And I just did a package-refresh-contents.

Strange, on http://stable.melpa.org/#/ the version is 0.14...

And on melpa (non-stable) there is a snapshot. So I guess I'm missing the stable repo.

Check your init.el

see what repo's you're referencing

emacs now always pulling the latest 20170126.717 version, not the version from melpa-stable. How can I set melpa-stable to have a higher priority then melpa in the repo list? Maybe I have to remove melpa.

Thats seemed to have worked.

Yessss... I've got a debugger ^^

🎉

You could pin melpa stable for cider in your init.el as well. that way you can have melpa in the list at the same time as melpa-stable (add-to-list 'package-pinned-packages '(cider . "melpa-stable") t)

Ohh, nice! Thanks @agile_geek

@benedek hmm, I have got problems around cider-jack-in-clojurescript as I can't start cider repls in a cljs/clj project. I get no error messages other than that warning in the nrepl messages but the CIDER repls just don't start

I haven't time to debug this. What's a safe way of regressing to an earlier version of CIDER?

you are on latest snapshot?

if so just nuke your cider installation in your .emacs.d change your config to melpa-stable and reinstall

if you use use-package just add :pin melpa-stable to your package config

not easy to go back to a previous snapshot i am afraid...

No I'm on latest stabel but it's not working

@agile_geek are you running melpa or melpa stable

Ah OK

I need to go back to 0.12.x

Can you visit the messages buffer

Maybe there's some info in there

Checked that

nothing

Also turn on nrepl logging

done

nothing

And check out what's happening in the

Damn

And that's 0.14?

Yes

nrepl starts

H

cider buffers don't

no messages

What do you mean nrepl starts

nrepl buffer is up with normal messages for figwheel etc and I can connect to the app but there are no cider buffers and I can't see a message that mentions the repl port so I can't cider-connect

I haven't got time to debug I've lost hours to this already

ah

i'm sorry

@agile_geek last question, none of your buffer shows cljs-user or is writing to you to connect browser to it?

don't understand the question

Oh I see

There's no cider repl buffers

Sorry yeah, not very well asked 😀

the only buffer is nrepl

so no

Ok

is your only option to blow away cider and reinstall an old version?

Back to me question above - how do I regress to early version of cider

Yep

since you are committed to completely eradicating cider, do you mind trying melpa's version, 0.15 snapshot?

and trying to jack in once and if it doesn't work you've lost hopefully 4 minutes

but with the upside that maybe it works?

and to ask a few questions, have you upgraded emacs recently?

could this be a discrepancy in byte compiled files versus the el files?

perhaps you could find ./ -name \*.elc | xargs rm and then restart emacs

^ obviously from within the cider directory

i upgraded 24.x to 25 recently on my windows machine and there were some changes to the byte compiler i guess

also, I've found that tracking github to be the easiest way to revert/upgrade/downgrade

;; load local version of cider
(add-to-list 'load-path "~/projects/cider")
(load "cider")

and this way you can just checkout which tag you care for

but it looks like melpa stable doesn't keep old versions around: https://github.com/melpa/melpa/issues/3948

@dpsutton to answer your question about upgrading emacs - no I haven't as it's too scary for this exact reason

haha i understand

you reminded me I've got all this in github so trying to restore from there

excellent!

i was just looking for least painful

although i still think you should try the latest from melpa stable

especially since you could run a git checkout to restore it

I did try latest from melpa stable...that's what broke everything

oh sorry i mean from melpa

i refactored some things with connections that should improve cljs and cljc actions

snapshot - will do but I'm back running and I've work to do

ah glad you're urnning then

if you want to ping me later when you do want to experiement i'm happy to help. and totally understand if you just want to get work done and ignore all this

May experiment at weekend but I'm really busy atm

How do I associate a buffer with a running cider repl?

@borkdude almost literally cider-assoc-buffer-with-connection

I tried that, but from a .cljc file it probably doesn’t work right?

What I’m trying to do is test a change from a library I’m using against my session

@borkdude I'm working on that. That feature (which requires some cleanup) is coming soon

but you can do it easily now

(cider-find-connection-buffer-for-project-directory
                                      nil :all-connections)

(setq-local cider-connections (list other-conn))

this will work most easily if you are on the most recent version of cider as there was a cleanup of session/connection

so that the two wouldn't get out of sync

but this should work for you

the former function will list all connections. Set it to some var and then setq a buffer local as (list connection-you-want). Connections are in simple terms just repl buffers

@borkdude

`

simple function that should get you there while i finish it. it'll take a while to get it polished and done

and just choose the repl as the connection you want

@dpsutton thanks!

Let me know if it works and if it needs a little tweaking

@dpsutton When I do C-x C-e it complains it needs a Clojure REPL

After I chose set-local-connection to the REPL buffer

Are you on most recent cider?

0.14.0-SNAPSHOT

And you ran it from the buffer you want to change the connection?

It is sensitive to the buffer it is run from

Yes, I ran it from core.cljc within the cljs-ajax library

https://www.dropbox.com/s/fj65yogmprojmg5/Screenshot%202017-01-27%2022.15.27.png?dl=0 https://www.dropbox.com/s/romgb4aupdaycwq/Screenshot%202017-01-27%2022.15.35.png?dl=0

can you eval (cider-current-connection) from the buffer?

not M-x but M-: eval

It seems to return nil

hmm

let me think and test on my machine

but my guess is if you upgrade cider it will work. current melpa is 15-snapshot

the reason it will work if you upgrade is that the code used to reach out willy nilly and ask for current connection

I have tried to make that only take a connection at the beginning

so now it starts with a connection and never asks for one again

It doesn’t have a high priority for me right now, so don’t worry too much about it

no problem

But I’ll upgrade when I’m less tired, soonish

but this is being worked on 🙂

i want connections to be first class citizens

so you start the eval chain with one and it honors that all the way through

this will make cljs and cljc buffers nicer as well

but removing the "one connection" assumption is tricky

it got baked in a lot

yeah

Hello everyone, my emacs frame gets wider when I only select buffer with cojure mode and that is only after cider-jack-in, this doesn't happen elsewhere. Any help?

@agile_geek: Emacs 25.1 or greater is required for latest stable cider versions

i don't know why my setq-local didn't work

i don't believe that's true, @jr0cket

support goes back to 24.4 i think

Depends which version of Cider you used

cider-compat.el is still in the project

and defines when-let and if-let

;; Pretty much everything here's copied from subr-x for compatibility with
;; Emacs 24.4.

In November Cider stopped working on Emacs 24.4 due to removal of cider-compat.el. A fix was applied but I was still seeing people with problems after that. It may be due to the version of cider, could be just snapshots, I havent had chance to test it myself. So I have recently recommended Emacs 25.1. Happy to be wrong though