Details
-
Bug
-
Resolution: Unresolved
-
Major - P3
-
None
-
3.5.0
-
None
Description
A bug, CDRIVER-3405, caused retryable-reads/writes watch tests to propagate errors from first attempt failures even if the second attempt succeeded. Now that CDRIVER-3405 is fixed we should assert that errors are only thrown from retryable watch operations if the operation has an error label true.
Attachments
Issue Links
- depends on
-
CDRIVER-3405 Creating a change stream after retryable error fails even with retryReads=true
-
- Closed
-