Skip to content
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

Bump mongodb from 2.2.36 to 3.6.3 #3

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Nov 26, 2020

Bumps mongodb from 2.2.36 to 3.6.3.

Release notes

Sourced from mongodb's releases.

v3.6.3

The MongoDB Node.js team is pleased to announce version 3.6.3 of the driver

Release Highlights

MongoError: not master when running createIndex

A regression introduced in v3.6.2 meant that createIndex operations would not be executed with a fixed primary read preference. This resulted in the driver selecting any server for the operation, which would fail if a non-primary was selected.

Performance issues on AWS Lambda

The driver periodically monitors members of the replicaset for changes in the topology, but ensures that the "monitoring thread" is never woken sooner than 500ms. Measuring this elapsed time depends on a stable clock, which is not available to us in some virtualized environments like AWS Lambda. The result was that periodically operations would think there were no available servers, and the driver would force a wait of heartbeatFrequencyMS (10s by default) before reaching out to servers again for a new monitoring check. The internal async interval timer has been improved to account for these environments

GSSAPI AuthProvider reuses single kerberos client

A regression introduced in v3.6.0 forced the driver to reuse a single kerberos client for all authentication attempts. This would result in incomplete authentication flows, and occaisionally even a crash in the kerberos module. The driver has been reverted to creating a kerberos client per authentication attempt.

Performance regression due to use of setImmediate

A change introduced in v3.6.1 switched all our usage of process.nextTick in the connection pool with setImmediate per Node.js core recommendation. This was observed to introduce noticeable latency when the event loop was experiencing pressure, so the change was reverted for this release pending further investigation.

Community Contributions

  • @jswangjunsheng submitted a fix for a rare scenario when wait queue members time out before connection establishment
  • @through-a-haze submitted a fix for incorrect construction of an X509 authentication message
  • @andreialecu helped us indicate peer optional dependencies in our package.json for stricter package managers (pnpm, yarn2)

Documentation

Reference: http://mongodb.github.io/node-mongodb-native/3.6/ API: http://mongodb.github.io/node-mongodb-native/3.6/api/ Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.6/HISTORY.md

We invite you to try the driver immediately, and report any issues to the NODE project.

Thanks very much to all the community members who contributed to this release!

Release Notes

... (truncated)

Commits
  • 86ae813 chore(release): 3.6.3
  • 308f840 chore: ensure aws4 is present for mongodb-aws tests
  • 9110a45 fix: correctly assign username to X509 auth command (#2587)
  • c9f9d5e fix: revert use of setImmediate to process.nextTick (#2611)
  • 89b77ed fix: Change socket timeout default to 0 (#2572)
  • 033b6e7 fix: move kerberos client setup from prepare to auth (#2608)
  • f0cee7a test: restrict geoSearch tests to mongodb <= 4.4 (#2612)
  • 186090e fix: add peerDependenciesMeta to mark optional deps (#2606)
  • cafaa1b fix: connection leak if wait queue member cancelled
  • 79df553 test: removes destructuring, spread, rest syntax and adds lint rules
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code labels Nov 26, 2020
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Feb 3, 2021

Superseded by #10.

@dependabot dependabot bot closed this Feb 3, 2021
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/mongodb-3.6.3 branch February 3, 2021 06:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file javascript Pull requests that update Javascript code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants