boot 2018-02-24 | Slack Archive

seancorfield00:02:39

I noticed the BOOT_WATCHERS_DISABLE env var (and --disable-watchers option) -- I'm seeing a lot of FSEvent errors with our huge project so I figured disabling watchers would help... but what is the downside of disabling watchers? What Boot behavior is affected? (I see @alandipert mentioned in the thread around the PR that introduced this)

richiardiandrea00:02:13

@seancorfield there is also a PR by @bhagany that I found out influences watch, I don't know if the behavior I saw affects also your big project, but it might be worth a try, it basically lazy watches

seancorfield04:02:15

For now, setting BOOT_WATCHERS_DISABLE=yes in ~/.boot/boot.properties has stopped the huge wall of FSEvent errors I was seeing on macOS. I guess my my question/concern is: what functionality do the watchers enable? If you're just running one-off tasks and one-off builds, is there any downside to disabling watchers?

minikomi09:02:50

I definitely had this problem on a project with a lot of nested folders containing images in my repositories dir.. ended up moving them into another folder and adding them into target when doing builds using io. I opened an issue at the time but there hasn't been much movement.

minikomi09:02:17

https://github.com/boot-clj/boot/issues/641

minikomi09:02:49

https://github.com/boot-clj/boot/issues/248 Also seems related

seancorfield04:02:07

I'm thinking I might set that on all of our servers where we run Boot tasks...

dominicm09:02:39

The option was added for CI

dominicm09:02:53

I think, unless you use the watch task, you'll be okay

2018-02-24

Channels