Fork me on GitHub
#cider
<
2015-10-27
>
michal20:10:53

hi. latest cider requires nREPL 0.2.11 to work correctly and look like I have 0.2.8. how may I bump this version up?

michal20:10:46

ok, never mind. i’ve just found missing dependency. i should talk more to myself simple_smile

bozhidar20:10:58

there’s also a section about this in the README

bozhidar20:10:12

just for some context - nREPL 0.2.11 introduced source location tracking which is a super important feature for a project like CIDER

bozhidar21:10:03

basically, when you use interactive evaluation on some vars they’d be created with the proper location metadata (source file, line, column)

bozhidar21:10:14

which makes it easy to jump to them afterwards

bozhidar21:10:24

previously this worked only when using load-file

bozhidar21:10:50

and with a few hacks it worked in a limited manner for interactive evaluation

bozhidar21:10:06

TL;DR - you want to use nREPL 0.2.11 with CIDER simple_smile

michal21:10:35

wow. it’s really impressive, thanks for info! one thing I noticed btw. is that repl throws mysterious exception once I end up session in emacs and try to connect to repl again (via cider-connect). is that expected behaviour?

michal21:10:37

ERROR |  Unhandled REPL handler exception processing message {:op init-debugger, :print-level 10, :print-length 10, :id 7}
java.net.SocketException: Socket closed
	at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:116) ~[na:1.8.0_65]
	at java.net.SocketOutputStream.write(SocketOutputStream.java:153) ~[na:1.8.0_65]

michal21:10:43

something like this

bozhidar21:10:36

hmm, that’s new

bozhidar21:10:45

report an issue and we’ll take a look at it

michal21:10:54

sure, thanks.

bozhidar21:10:59

seems to be something related to the debugger

bozhidar21:10:13

but without some repro steps and playing with the code myself I can’t be sure

michal21:10:14

i noticed that few cider version ago

michal21:10:35

and it’s still reproducible with the newest one