This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2015-11-28
Channels
- # admin-announcements (21)
- # beginners (102)
- # boot (8)
- # cider (40)
- # cljsrn (2)
- # clojure (52)
- # clojure-nl (2)
- # clojure-russia (6)
- # clojure-taiwan (2)
- # clojure-uk (1)
- # clojurescript (363)
- # datavis (22)
- # datomic (69)
- # emacs (4)
- # hoplon (1)
- # immutant (2)
- # jobs-rus (13)
- # ldnclj (6)
- # lein-figwheel (2)
- # leiningen (9)
- # liberator (1)
- # off-topic (1)
- # om (68)
- # onyx (28)
- # parinfer (3)
Reminder to donate to cider https://www.bountysource.com/teams/cider
I know I’ve asked this before.. but it’s that time of year where I attempt a cider update
My first problem is that M-x package-refresh-content
hangs with Contacting host:
. Anyone know a solution to this?
I don’t think the packages list has been successfully updated since M-x list-packages
lists cider 0.8.2 as the latest version
use http://stable.melpa.org instead
Ok, so I should change to the correct hosts then. I currently have the following setup:
is http://stable.melpa.org the only one I need?
but yeah - if you’re interested only in “stable” releases you need only melpa stable
but what I don’t understand is why my package list isn’t updated when I run M-x package-refresh-contents
(setq url-http-attempt-keepalives nil)
solved the issue for now. At least I can see cider 0.9.1 listed now
Ok, now when I run M-x package-install [RET] cider [RET]
I get "package-compute-transaction: Package `highlight-0' is unavailable"
@malabarba invested a lot of time in improving it
@bozhidar: I got it working in the end. For some reason it worked when I M-x list-packages and manually clicked the package
I tested the debugger… nice! One problem I saw was the following NPE in a multithreaded contex: java.lang.NullPointerException at clojure.core$deref_future.invoke(core.clj:2186) at clojure.core$deref.invoke(core.clj:2207) at cider.nrepl.middleware.debug$skip_breaks_QMARK_.invoke(debug.clj:57)
@malabarba: stable
@malabarba: Basically what I did was start a http server (jetty) and add a breakpoint on one of the functions that gets called when I visit an http endpoint. That’s when I saw the NPE
@malabarba: nice!
Yeah. The debugger was deeply rewritten. It plays much nicer with pretty much everything. ☺️
@malabarba: Any idea when the next stable release will be?