Figure out why prospector (and maybe other tools) makes the boussole watcher go crazy
I've been noticing this more and more recently because it puts a heavy load on my dev VM whenever it happens. I have no idea where the "fault" lies here, whether it's Vagrant, Virtualbox, prospector, boussole, watchdog, or something else.
While prospector is running on the Tildes codebase, it's extremely common (but may not always happen?) for the boussole service to detect that all of the SCSS files have been "deleted" and then "created" in the same location. Because every single deletion and creation event triggers a rebuild of the CSS, this results in boussole building the CSS hundreds of times in the background, completely unnecessarily. If I watch the boussole logs while prospector is running and restart the service as soon as I see it get into this mode, it even seems to happen multiple times in the same run (seems to happen towards the end of the process).
I don't have any ideas about what might be causing this. It's especially strange because prospector shouldn't even be looking at or touching any SCSS files at all. A possible approach may be stepping through a prospector run to narrow down at what point this happens (if it's even consistent).