I'm writing a small terminal UI on top of shake, and want to display a progress bar, as demonstrated in this screenshot given below [1] However, depending on the frequency at which the IO Progress action is polled, and exactly when the progress-tracking thread is killed, I get one of two results:

• skipped: 178, built: 1 (see footnote 2)

  

• unknown: 178, built: 1

  

How does one get predictably notified of the of end of a build, along with the final stats? Why leave the polling to the library's user? Why doesn't shake take a polling frequency and callback function itself? And ensure the callback function is called one final time right after the build ends?

This could be related to #361, perhaps.

[1] ignore the graphical bar, I'm trying to figure out the numerical stats right now.

[2] I don't completely understand why there are two rules being built in certain runs, and only one rule in certain runs. I'm not touching anything on the filesystem, just changing the polling frequency.