I did a search on this but didn't see anything other than the acknowledgement that people were seeing this bug. Is this bug (I've beta v.41) close to being squashed? Pending that, is there a way to manually set that number back to something reasonable (like zero)? Just curious.

-Zeke