Fork me on GitHub
#boot
<
2017-08-16
>
seancorfield01:08:51

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.

seancorfield01:08:20

That was a bit of a surprise. Is this expected behavior? I mean, expected by the Boot team 🙂

seancorfield01:08:00

It looks like it's to do with how the shim starts the Clojure RT up maybe...

micha01:08:17

boot starts multiple instances of clojure

micha01:08:32

each pod is a separate instance of the clojure runtime

seancorfield01:08:42

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.

seancorfield01:08:01

That's... unfortunate...

seancorfield01:08:32

I guess the trick would be to start the REPL, set that as a system property, and then start a new pod maybe?

seancorfield02:08:50

(yeah, that works)

seancorfield02:08:20

(this was primarily to test some code that needed to interact with a Clojure Socket Server REPL)

pesterhazy02:08:47

@seancorfield to start a socket server from Boot, these two approaches should also work: https://github.com/Unrepl/unravel#launching-a-socket-repl

seancorfield02:08:56

@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.

seancorfield03:08:30

@pesterhazy Also... I need to watch your Unravel preso from EuroClojure 🙂

danielcompton21:08:18

Is it possible to put out a boot alpha release? We really need the fix to boot_watchers_disable for CI

micha21:08:58

i can have a look tonight

juhoteperi21:08:17

I've been running 2.7.2-SNAPSHOT everywhere for weeks

juhoteperi21:08:39

I think it would be fine to just release current master as 2.7.2

seancorfield21:08:13

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?

juhoteperi21:08:58

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

richiardiandrea21:08:28

Ready to merge a few outstanding PRs if necessary

ghadi21:08:46

Addressing or merging https://github.com/boot-clj/boot-bin/pull/4 would also be excellent before the next release.

juhoteperi21:08:49

boot-bin versioning is separate from boot, but yeah, that should also be released