-
Notifications
You must be signed in to change notification settings - Fork 1.8k
test(NODE-4262): simplify leak checker for startSession fixes #3281
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
Conversation
0aba7e2
to
f7c9172
Compare
7d0afae
to
ab5683d
Compare
Co-authored-by: Bailey Pearson <[email protected]>
test/integration/client-side-encryption/client_side_encryption.spec.test.js
Outdated
Show resolved
Hide resolved
...(isAuthEnabled | ||
? skippedAuthTests.concat(skippedMaxWireVersionTest) | ||
: [skippedMaxWireVersionTest]), | ||
// TODO(NODE-4288): Fix FLE 2 tests |
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.
should we leave a comment on Durran's current fle2 spec sync PR (NODE-4251) to rebase so that we can make sure to keep things consistent?
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.
Linked the jira, commented on GH, will comment on JIRA in a sec. I needed to skip these to check that there wasn't something hanging the run related to these changes.
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.
I didn't look at the code in too much detail, I just have this question, the coordination question above, and also - don't we have a NODE ticket that this work can be attached to?
Description
What is changing?
Make the leak checker operate on MongoClient and ServerSessionPool.
What is the motivation for this change?
Simplifies the tracking of resources for the forthcoming change where sessions are managed on the client instead of the topology.
Double check the following
npm run check:lint
script<type>(NODE-xxxx)<!>: <description>