Fork me on GitHub
#cider
<
2018-07-12
>
euccastro02:07:51

getting this now right after cider-jack-in (no custom cider-clojure-cli-parameters):

[nREPL] Starting server via /usr/local/bin/clojure -Sdeps '{:deps {org.clojure/tools.nrepl {:mvn/version "0.2.13"} com.billpiel/sayid {:mvn/version "0.0.16"} refactor-nrepl {:mvn/version "2.4.0-SNAPSHOT"} cider/cider-nrepl {:mvn/version "0.18.0-SNAPSHOT"}}}' -e '(require (quote cider-nrepl.main)) (cider-nrepl.main/init ["com.billpiel.sayid.nrepl-middleware/wrap-sayid", "refactor-nrepl.middleware/wrap-refactor", "cider.nrepl/cider-middleware"])'...
[nREPL] server started on 35964
[nREPL] Establishing direct connection to localhost:35964 ...
[nREPL] Direct connection to localhost:35964 established
error in process filter: nrepl-send-sync-request: Sync nREPL request timed out (op clone id 1)
error in process filter: Sync nREPL request timed out (op clone id 1)

euccastro02:07:51

if I try and switch to the REPL buffer, it shows up as an empty buffer with name *cider-uninitialized-repl*

euccastro03:07:39

if anyone else is experiencing this, a workaround is to set cider-clojure-cli-parameters to "-e '(require (quote cider-nrepl.main)) (cider-nrepl.main/start-nrepl {:middleware %s})'"

bozhidar05:07:50

> right. so i believe the alias cider-current-connection was added back so that older tooling and newer tooling had the same vocabulary

bozhidar05:07:29

@dpsutton Ah, yeah. Now I remembered what happened - Vitalie meant to add aliases since the beginning but he forgot or something like this.

dpsutton12:07:00

exactly. and it looks like spacemacs reacted at the very moment those things changed.

bozhidar05:07:27

@hagmonk Just woke up and left some review.

bozhidar05:07:37

Overall things are looking good and my comments are mostly minor.

hagmonk05:07:20

@bozhidar I am still not asleep, so I will take a look now :)

bozhidar05:07:14

@hagmonk Thanks!

hagmonk06:07:43

@bozhidar after pushing changes, looks like all but one test passed (CLJS test timed out)

bozhidar06:07:06

Yeah, those fail randomly from time to time.

bozhidar06:07:12

Can’t be related to your changes.

bozhidar06:07:40

I’ve pushed a new snapshot, hopefully now the problem is solved for everyone.

hagmonk06:07:06

me too! sorry for extending it a day

dominicm06:07:31

thus solving the problem once and for all

bozhidar08:07:42

nREPL now has an official manual http://nrepl.readthedocs.io/en/latest/ It’s still pretty much a work in progress (mostly a restructuring of the old README) and your help improving it would be appreciated! (http://nrepl.readthedocs.io/en/latest/about/contributing/#working-on-the-manual)

andrea.crotti09:07:15

I'm having a very strange issue where the Cider CLJ repl doesn't load the user.clj file

andrea.crotti09:07:37

the weird thing is that it was working fine yesterday and I don't think I changed anything

andrea.crotti09:07:07

lein dev however works so leiningen actually loads that correctly

andrea.crotti10:07:14

tried now with both 0.17 and 0.18-snapshot and it's the same, not even sure it's a problem with Cider to be fair but anyone had issues loading user.clj files?

andrea.crotti10:07:34

ok checking out the project again with the asme exactly config and no untracked files works, so whatever it is is not related with Cider

andrea.crotti10:07:53

I even did a couple of lein clean but there must be still something there that made it fail

bozhidar11:07:34

OK, a problem that solves itself (at least for me) - my favourite kind. 🙂

andrea.crotti12:07:11

yeah when they solve themselves without apparent reason is not great, but well 😄

andre.stylianos15:07:57

Yep, sorry. My fault. I changed that in spacemacs but didn't account for people who had cider pinned to the stable version, since spacemacs defaults to the snapshot version. I opened a PR with the fix using cider-current-connection instead of cider-current-repl

andre.stylianos15:07:50

it's already merged by the way 😳

mikerod15:07:28

I think I’ve seen this here befoer, but cannot remember, when doing something like cider-jack-in can you go back and see the command that was ran (shows up briefly in minibuffer), and also can you see any output/error it resulted in?

eggsyntax15:07:47

Probably in messages

mikerod16:07:34

@ oh, thanks there is some stuff there!

mikerod16:07:39

I should have guessed

eggsyntax15:07:55

er, *messages*

eggsyntax15:07:13

Yeah, just confirmed. There's also *cider-error* IIRC, for errors thrown by the REPL after it's started up. Also the nrepl-server buffer occasionally has useful info.

kwcharllie37915:07:48

Does anyone has a problem with macroexpanding with Node repl, the newest clojurescript and the newest cider?

(ns serverless-cljs-lambdas.core
  (:require [cljs-lambda.macros :refer [defgateway]]))

(defgateway echo [event ctx]
  {:status  200
   :headers {:content-type (-> event :headers :content-type)}
   :body    (event :body)})
Expanding on defgateway simply returns itself.

mikerod17:07:19

(related to question that was answered earlier for me here) So when looking at *Messages* buffer to see the cmd that is used for cider-jack-in I see something like this:

Starting nREPL server via /usr/local/bin/lein update-in :dependencies conj \[org.clojure/tools.nrepl\ \"0.2.13\"\ \:exclusions\ \[org.clojure/clojure\]\] -- update-in :plugins conj \[refactor-nrepl\ \"2.4.0-SNAPSHOT\"\] -- update-in :plugins conj \[cider/cider-nrepl\ \"0.16.0\"\] -- repl :headless :host ::...
At the end, the repl :headless :host ::... part, what are the ... ? Is this Emacs truncated this somehow ( I don’t see any way to tweak this), or is Cider truncating (can’t find that in cider source either0, or does the cmd actually end in ...?

baptiste-from-paris19:07:08

hello friends, am I the only one to have this behavior with cider 0.17

(for [x (range 4)]
        (println x))

=> 1
=> 2
=> 3 IN CLJ

=> 123 IN CLJS

baptiste-from-paris19:07:27

it makes me crazy when I want to (dir 'namespace)

dpsutton19:07:51

I am observing

(for [x (range 4)]
  (println x))
0
1
2
3
(nil nil nil nil)
in both clj and cljs repls

dpsutton19:07:17

i'm on 0.18-snapshot that is very up to date but not on the latest commit i'm sure

eggsyntax19:07:17

I'm on 0.17, and I'm seeing the same behavior that @baptiste-from-paris reported.

baptiste-from-paris19:07:38

seems to be a cljs stuff

eggsyntax20:07:19

Funny, I don't remember that behavior from when I was on 17 before for a long time (I just switched back to 17 yesterday until 18 stabilizes).

euccastro20:07:07

they aren't part of the command, and they don't mean the command is being truncated. just ignore them?

mikerod20:07:27

Ah ok. Thanks for showing me where it is!