When a single parent node's status changes, it causes a cascade of updates to child nodes. All of those updates report separate StateChanges, frequently causing multiple identical lines to be printed. Adding a very small debounce to the update monitoring avoids this noise while hiding only the most ephemeral state transitions.
ptarjan
commented
8 years ago
When a single parent node's status changes, it causes a cascade of updates to child nodes. All of those updates report separate
StateChanges, frequently causing multiple identical lines to be printed. Adding a very small debounce to the update monitoring avoids this noise while hiding only the most ephemeral state transitions.r? @ptarjan