-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(NODE-6454): use timeoutcontext for state machine execute() cursor options #4291
Conversation
LGTM, I'll wait for CI to finish before approving Edit: I'll wait for the end to end test case before approving |
569462e
to
666575d
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Lint is failing, I'll wait on re-reviewing until it's fixed
f1f5d0d
to
5660c45
Compare
.catch(e => e); | ||
it( | ||
'the bulk write operation times out', | ||
mergeTestMetadata(metadata, { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should fix some of the flakiness we see in CI.
5660c45
to
91f2b34
Compare
Description
What is changing?
Instead of using the remainingTimeMS as the value for
timeoutMS
when running cursor operations in the state machine, we provide a CursorTimeoutContext that wraps the original timeout.Is there new documentation needed for these changes?
What is the motivation for this change?
Double check the following
npm run check:lint
scripttype(NODE-xxxx)[!]: description
feat(NODE-1234)!: rewriting everything in coffeescript