This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-21
Channels
- # admin-announcements (4)
- # beginners (41)
- # boot (46)
- # cider (8)
- # clojure (132)
- # clojure-austin (15)
- # clojure-belgium (3)
- # clojure-greece (3)
- # clojure-hk (1)
- # clojure-mexico (4)
- # clojure-quebec (5)
- # clojure-russia (46)
- # clojure-spec (225)
- # clojure-taiwan (1)
- # clojure-uk (17)
- # clojurescript (46)
- # clojurewerkz (1)
- # core-async (28)
- # cursive (9)
- # datascript (3)
- # datomic (5)
- # defnpodcast (42)
- # devcards (60)
- # emacs (27)
- # hoplon (7)
- # lein-figwheel (5)
- # leiningen (12)
- # mount (8)
- # om (13)
- # play-clj (2)
- # reagent (47)
- # rethinkdb (5)
- # ring-swagger (7)
- # spacemacs (9)
- # specter (12)
- # testing (1)
- # untangled (1)
- # vim (11)
- # yada (31)
Really strange: If I run the bit of fireplace that gets the classpath and path separator, the bdecoder fails. No idea why, or how this runs normally in fireplace, or even if it does? Maybe it just gets swallowed on Lein!
However, I have found the real culprit. For whatever reason, when evaluating code in Figwheel with an id, the output goes to the ORIGINAL id, not the new id.
So the '1' is in the output, but it's not picked up as belonging to the current operation.
For some reason, it also locks up figwheel on subsequent requests when I do it. Probably because we're looking in the wrong id again
YEP. That's it! It goes to the original "id" not the new one, so it gets lost. Fireplace filters differently to other editors I would guess. I think CIDER uses a subscribe system, where it listens to everything to build it's CLI.
It only locked up once, I fiddled with the code a little. It's mildly worrying, but not hugely concerning.
But yes, it keeps printing output to the id I used to create the session for figwheel.
I don't know how to push further. I guess look through figwheel source / report to @bhauman
https://clojurians.slack.com/archives/clojurescript/p1469104022000508 in case someone wants to jump in before me
@dominicm: I'm still having problems with Figwheel snapshot... hmm
@juhoteperi: hmm indeed. I'll dig in tomorrow. I was hopeful it would just work