RUBY-2523 Client Side Operations Timeout #2881
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Co-authored-by: Jamis Buck <[email protected]>
* extract Mongo::Error::OperationFailure::Family * add server timeout error, raised when error code == 50 * silence FLE errors on latest server * only raise ServerTimeoutError when csot timeout is present on the context * consolidate timeouts under TimeoutError * reorder exception handlers to accomodate new base class for socket timeout errors
* starting on the op_msg timeout refactoring * make sure classes with custom message() implementions set the timeouts * add more tests
* cursors CSOT * need to add context as parameter * wups, maxTimeMS, not timeoutMS * there is no msg variable here * context#timeout_ms is not actually used anywhere
* change stream specs pass * collateral damage * tweak timeouts for jruby * more timeout tweaks to accommodate jruby
* bump drivers-evergreen-tools * skip failing tests on latest (RUBY-3464) * Add single-node replica set configuration * Do not run csot spec tests on regular configurations * move spec/shared back to master after merging spec/shared PR * test CSOT against all the dbs * do not refresh the context, just update the one variable otherwise, a "cursor_lifetime" cursor will have its deadline inadvertently refreshed immediately after the "find" command, which messes up the deadline check * fix issues with change stream timeouts * only run CSOT specs against one DB version * skip failing specs on latest (pending SERVER-90047) * correct bogus error during tests * skip "range" tests on latest (pending RUBY-3423) * try fixing broken lambda tests something still wrong here, now getting a missing library when doing `sam build`? --------- Co-authored-by: Dmitry Rybakov <[email protected]>
Co-authored-by: Jamis Buck <[email protected]>
|
There is an existing patch(es) for this commit SHA: Please note that the status that is posted is not in the context of this PR but rather the (latest) existing patch and that may affect some tests that may depend on the particular PR. If your tests do not rely on any PR-specific values (like base or head branch name) then your tests will report the same status. If you would like a patch to run in the context of this PR and abort the other(s), comment 'evergreen retry'. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.