Fork me on GitHub
#cider
<
2015-12-14
>
bozhidar07:12:42

package.el is not the best package manager is the world, unfortunately

bozhidar07:12:03

other than pinning some packages to specific versions there’s little one can do

bozhidar07:12:43

obviously if someone wants only stable package releases the simplest solution is to just disable melpa and use only melpa stable

jstew14:12:52

@bozhidar: RE: Using melpa stable, does it work alright with prelude? I've thought about switching over to stable completely but I'm afraid it could mess other things up.

jstew14:12:15

Right now, I have stable added to the list of package sources and just have cider and clojure-mode pinned.

bozhidar14:12:18

nope, some packages prelude uses are only on MELPA

bozhidar14:12:41

or haven’t had releases recently

jstew14:12:48

Good to know. Thanks.

jonpither17:12:20

hi - a few of us are chatting that if you try to a big compile, or namespace refresh just after a CIDER REPL launches, then you sporadic compilation errors

jonpither17:12:36

I've had this for a while but blamed my own setup, but I think it's a CIDER issue

jonpither17:12:52

is it a known issue?

jonas17:12:40

@jonpither: I think I’ve seen this. I have no idea if it’s a CIDER issue or not

jonpither17:12:36

You need to wait for the initial ns scan to finish before you do anything

jonpither17:12:49

which isn't great

robert-stuttaford19:12:22

definitely experience this as well

robert-stuttaford19:12:41

it would be nice to know that a) it’s still busy and then b) it’s done

robert-stuttaford19:12:49

via output in the repl buffer. i could totally live with that

bozhidar19:12:04

file a ticket

bozhidar19:12:16

with some repro steps and will figure out a solution

robert-stuttaford19:12:55

rock paper scissors, jonpither? -grin-

cichli22:12:36

@jonpither @jonas I've encountered something similar - do either of you use refactor-nrepl? I think that warms some kind of analysis cache using tools.analyzer right after you connect

jonpither22:12:58

I do, and my colleagues do, so wouldn't surprise me

jonpither22:12:48

@bozhidar: @robert-stuttaford I can raise a GitHub, issue, but right now it would be vague (sometimes when I start a fresh REPL and try to compile, I get compilation errors). I think to repro you need a suitable large project

jonpither22:12:58

I'll raise it tomorrow

cichli22:12:33

Try putting (setq cljr-eagerly-build-asts-on-startup nil) in your config and see if it still occurs

jonpither22:12:00

@cichli: will do

cichli22:12:25

(had that in mine for a while now, but can't remember why...)

cichli22:12:09

& I also haven't had the compilation issue in a while

cichli22:12:18

Ah I remember - the reason I changed it was that it was causing weird issues when REPLing in to an already-running Clojure program with a system started - after connecting, lots of records would be instances of "old" versions of protocols, because something was re-evaluating everything. I tracked it down to the refactor-nrepl cache

jonpither22:12:16

I just created an issue by accident in CIDER

jonpither22:12:32

should really go to bed