This bug appears to have been introduced in
518dc82235528ebfd1834fca6dd64a9ccfb20d52. It appears that the only effect would have been that if an operator for a hunt was demoted, clients connected before the demotion would continue to see pending guesses for that hunt.
I found this via manual inspection of the source file when I was experimenting with trying to make use of Meteor 2.16's observeChangesAsync and observeAsync.
This bug appears to have been introduced in 518dc82235528ebfd1834fca6dd64a9ccfb20d52. It appears that the only effect would have been that if an operator for a hunt was demoted, clients connected before the demotion would continue to see pending guesses for that hunt.
I found this via manual inspection of the source file when I was experimenting with trying to make use of Meteor 2.16's
observeChangesAsync
andobserveAsync
.