You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* RUBY-1369 Collection change stream integration test
* RUBY-1369 try_next implementation
* RUBY-1369 Move to spec/integration
* RUBY-1369 Got try_next working when there are changes
* RUBY-1369 Test try_next with no changes
* RUBY-1369 Document try_next
* RUBY-1369 Change change stream resume logic more to retry once only
* RUBY-1369 Apply current resume behavior to try_next
* RUBY-1369 Add docstrings for change_stream_resumable?
* RUBY-1369 Document how to restart change streams and when they are resumed by the driver automatically
* RUBY-1369 failCommand is 4.0+ only
* RUBY-1369 These are now non-resumed
* RUBY-1369 Repair the logic yet again.
The concept of "retrying once" is apparently much more difficult than it first appears
* RUBY-1369 Repair this test again and try another way to not have it be stuck in a getmore loop
* RUBY-1369 Use timeout-interrupt to stop tests hanging forever on change stream reads
* RUBY-1369 Force a successful getMore prior to failing them.
I believe change stream drops documents upon a reset without startAtOperationTime,
hence right now we can't reliably test initial getMores failing
* RUBY-1369 Need to clear fail points only on tests using them if I want to run others on servers < 4.0
0 commit comments