This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-05-11
Channels
- # admin-announcements (10)
- # arachne (2)
- # beginners (74)
- # boot (302)
- # cider (49)
- # cljs-dev (11)
- # cljs-edn (7)
- # cljsjs (13)
- # cljsrn (1)
- # clojure (164)
- # clojure-austin (1)
- # clojure-brasil (3)
- # clojure-finland (2)
- # clojure-greece (4)
- # clojure-russia (48)
- # clojure-uk (11)
- # clojurescript (138)
- # community-development (1)
- # cursive (13)
- # datascript (1)
- # datomic (19)
- # emacs (4)
- # events (1)
- # garden (1)
- # hoplon (123)
- # jobs-discuss (9)
- # keechma (5)
- # lein-figwheel (4)
- # leiningen (2)
- # luminus (15)
- # mount (1)
- # off-topic (8)
- # om (66)
- # on (1)
- # onyx (28)
- # other-languages (2)
- # planck (1)
- # proton (5)
- # re-frame (18)
- # reagent (15)
- # untangled (15)
Sorry about the ungodly hour, but if someone could merge this it'd be great. https://github.com/clojure-emacs/cider-nrepl/pull/356
latest commit broke the cider-nrepl, it throws with see-also.edn not found. probably a wrong path at https://github.com/clojure-emacs/cider-nrepl/commit/089fda4c141208d2a896136a4eb9370deffd40b1#diff-7e5759ae416dd076f6227ef23d80414dR143 (`see-also.edn` seems to be packeded so it's in the root class-path, not under resources
)
@wagjo I just opened a PR to get feedback https://github.com/clojure-emacs/cider-nrepl/pull/357
I was really confused first because I was trying to use cider for org-babel so I was convinced it was something with my org-mode setup, then I tried it in another project and it also blew up
@plexus: Thanks for your workaround. I ran into the problem just now when doing a fresh install of cider on a new machine.
hehe no worries CIDER has been pretty stable lately and has seen a lot of new development, so that's great. People running from -SNAPSHOT
should be prepared for some occasional breakage
Hi, when I started CIDER today I saw the following error in Messages:
Starting nREPL server via /usr/local/bin/lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.12\"\] -- update-in :plugins conj \[refactor-nrepl\ \"2.3.0-SNAPSHOT\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.13.0-SNAPSHOT\"\] -- repl :headless...
error in process sentinel: nrepl-server-sentinel: Could not start nREPL server: Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=128m; support was removed in 8.0
clojure.lang.Compiler$CompilerException: java.io.FileNotFoundException: resources/see-also.edn (No such file or directory), compiling:(info.clj:143:38)
at clojure.lang.Compiler$InvokeExpr.eval (Compiler.java:3657)
clojure.lang.Compiler$NewExpr.eval (Compiler.java:2568)
clojure.lang.Compiler$InvokeExpr.eval (Compiler.java:3651)
clojure.lang.Compiler$DefExpr.eval (Compiler.java:451)
clojure.lang.Compiler.eval (Compiler.java:6932)
My emacs has starting occasionally crashing in windows when using CIDER. Anyone seen this? Not saying CIDER is responsible. Just did a packages upgrade, hoping someone else is seeing..
Damn... at first I couldn’t pin-point what is going on Oh well, snapshot version at our own risk
coming back to see-also.edn
problem I deleted broken jar from my .m2 folder :
/Users/jan/.m2/repository/cider/cider-nrepl/0.13.0-SNAPSHOT:
total used in directory 3424 available 10493789
drwxr-xr-x 26 jan staff 884B May 11 12:22 .
drwxr-xr-x 23 jan staff 782B Apr 25 01:08 ..
-rw-r--r-- 1 jan staff 209B May 11 12:22 _maven.repositories
-rw-r--r-- 1 jan staff 322K Apr 25 01:08 cider-nrepl-0.13.0-20160424.042936-2.jar
-rw-r--r-- 1 jan staff 40B Apr 25 01:08 cider-nrepl-0.13.0-20160424.042936-2.jar.sha1
-rw-r--r-- 1 jan staff 3.2K Apr 25 01:08 cider-nrepl-0.13.0-20160424.042936-2.pom
-rw-r--r-- 1 jan staff 40B Apr 25 01:08 cider-nrepl-0.13.0-20160424.042936-2.pom.sha1
-rw-r--r-- 1 jan staff 323K May 4 11:50 cider-nrepl-0.13.0-20160504.055219-4.jar
-rw-r--r-- 1 jan staff 40B May 4 11:50 cider-nrepl-0.13.0-20160504.055219-4.jar.sha1
-rw-r--r-- 1 jan staff 3.2K May 4 11:50 cider-nrepl-0.13.0-20160504.055219-4.pom
-rw-r--r-- 1 jan staff 40B May 4 11:50 cider-nrepl-0.13.0-20160504.055219-4.pom.sha1
-rw-r--r-- 1 jan staff 323K May 10 09:57 cider-nrepl-0.13.0-20160508.163905-6.jar
-rw-r--r-- 1 jan staff 40B May 10 09:57 cider-nrepl-0.13.0-20160508.163905-6.jar.sha1
-rw-r--r-- 1 jan staff 3.2K May 10 09:57 cider-nrepl-0.13.0-20160508.163905-6.pom
-rw-r--r-- 1 jan staff 40B May 10 09:57 cider-nrepl-0.13.0-20160508.163905-6.pom.sha1
-rw-r--r-- 1 jan staff 769B May 11 11:35 maven-metadata-annadale.xml
-rw-r--r-- 1 jan staff 41B May 11 11:35 maven-metadata-annadale.xml.sha1
-rw-r--r-- 1 jan staff 769B May 11 11:35 maven-metadata-clojars.xml
-rw-r--r-- 1 jan staff 40B May 11 11:35 maven-metadata-clojars.xml.sha1
-rw-r--r-- 1 jan staff 234B May 11 11:35 resolver-status.properties
now, how can I force CIDER to user 20160508 version and not to download today version once again?
I’ve been pretty busy lately and haven’t been reviewing PRs as carefully as I usually do
It would be nice if the tests actually built and ran there jar so this doesn't happen again. I may take a swing at that later.
circleci is nice too
I just use travis by default, as a few years ago it was the only ci with the explicit goal of providing trivial github integration
We could set up an instance on AWS that builds and deploys the latest master. Travis already lets you ping a webhook when all builds pass, so they'd be trivial to integrate.