Error in oplog callback #1767
Closed
Error in oplog callback #1767
Comments
Looks like the update event from oplog triggered a callback after the query was stopped. |
Thanks! Analyzing the code, it seems most likely that this is the bug fixed by d30bb79. (This commit was able to be so simple because of fca2966, a refactoring inspired by this issue.) It's the only way I can see that that callback could have been called after the observe driver got stopped. (d868325 adds another assertion that makes it more clear that there's no other concurrency going on here.) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
@glasser running on the oplog-with-operators release:
The text was updated successfully, but these errors were encountered: