This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-08-16
Channels
- # aleph (1)
- # architecture (5)
- # beginners (43)
- # boot (23)
- # cider (5)
- # cljs-dev (143)
- # clojure (42)
- # clojure-austin (4)
- # clojure-dusseldorf (14)
- # clojure-italy (15)
- # clojure-norway (1)
- # clojure-russia (10)
- # clojure-spec (41)
- # clojure-uk (70)
- # clojurescript (262)
- # cursive (3)
- # data-science (18)
- # datomic (66)
- # figwheel (1)
- # fulcro (39)
- # hoplon (21)
- # jobs-rus (1)
- # juxt (4)
- # lein-figwheel (2)
- # leiningen (4)
- # lumo (26)
- # off-topic (4)
- # om (6)
- # onyx (19)
- # parinfer (50)
- # pedestal (9)
- # portkey (10)
- # re-frame (41)
- # schema (5)
- # spacemacs (2)
- # yada (35)
I thought Boot only started one JVM and one instance of Clojure but I just tried this BOOT_JVM_OPTIONS='-Dclojure.server.repl="{:port 55555 :accept clojure.core.server/repl}"' boot repl
-- thinking I could start a REPL with a Socket Server REPL running inside it -- and it failed with "Address already in use" during initialization.
That was a bit of a surprise. Is this expected behavior? I mean, expected by the Boot team 🙂
It looks like it's to do with how the shim starts the Clojure RT up maybe...
Just figuring that out from the boot.App
stuff... yeah, even the basic path start workers as well as core... so you can't safely pass -Dclojure.server.repl=...
into Boot.
That's... unfortunate...
I guess the trick would be to start the REPL, set that as a system property, and then start a new pod maybe?
(yeah, that works)
(this was primarily to test some code that needed to interact with a Clojure Socket Server REPL)
@seancorfield to start a socket server from Boot, these two approaches should also work: https://github.com/Unrepl/unravel#launching-a-socket-repl
@pesterhazy Yeah, I was really trying to simulate a Clojure process that started it up because of the system property but I got what I needed done in the end. I'd forgotten about the socket-server
task in Boot now... so boot socket-server --port 55555 repl
would have been close enough to what I wanted.
@pesterhazy Also... I need to watch your Unravel preso from EuroClojure 🙂
Is it possible to put out a boot alpha release? We really need the fix to boot_watchers_disable for CI
I've been running 2.7.2-SNAPSHOT everywhere for weeks
I think it would be fine to just release current master
as 2.7.2
Yup, we've also been running 2.7.2-SNAPSHOT everywhere for a while and it seems solid. It looks like you still have quite a few issues planned for a 2.7.2 "gold" release?
next-release has a few open issues, but those can just as well be fixed in 2.7.3 or what ever is the next release
Ready to merge a few outstanding PRs if necessary
Addressing or merging https://github.com/boot-clj/boot-bin/pull/4 would also be excellent before the next release.
boot-bin versioning is separate from boot, but yeah, that should also be released