Since merging in my co-worker's changes this morning, guard-livereload has stopped working. The javascript is being injected into the page, and guard does detect my browser, but no matter what files I modify, it simply does not reload whatsoever.
Here is my console output today, with livereload not working. Note that there is just zero output after detecting the browser - unlike other questions on stackoverflow, where livereload claims to be reloading but does not do anything. Here is my console output from the last time I was at work, when it did function correctly. The annoying thing is that ui.css.scss is the file I'm modifying now as well! My guardfile has not changed, I've checked.
Here is my bundle install output from this morning (my co-worker updated a bunch of gems). I'm using rack-livereload in lieu of a browser extension.
Any advice?
UPDATE: I've tried using the Livereload Chrome extension, but I get exactly the same (lack of) output, so I don't believe rack-livereload to be the culprit.
Found the solution, in part thanks to this.
It turns out Sublime Text 3's atomic save feature is what was preventing LiveReload from detecting changes to Sass files. Why it worked before a certain commit is beyond me...
Simply add "atomic_save": false to your Sublime settings to avert this.