search

qlik-oss / core-grpc-mongodb-connector

Example connector written in Node.js for MongoDB using the gRPC data-loading API in Qlik Associative Engine.
MIT License
5 stars 3 forks source link

Update dependency mongodb to v3.5.8 #197

Closed renovate[bot] closed 4 years ago

renovate[bot] commented 4 years ago

This PR contains the following updates:

Package Type Update Change
mongodb dependencies patch 3.5.7 -> 3.5.8

Release Notes

mongodb/node-mongodb-native ### [`v3.5.8`](https://togithub.com/mongodb/node-mongodb-native/releases/v3.5.8) [Compare Source](https://togithub.com/mongodb/node-mongodb-native/compare/v3.5.7...v3.5.8) The MongoDB Node.js team is pleased to announce version 3.5.8 of the driver ##### Release Highlights ##### [Fixes for NEAREST latency window calculation](https://jira.mongodb.org/browse/NODE-2407) [@​adityapatadia](https://togithub.com/adityapatadia) helped uncover an issue with our server selection logic which filtered out servers after evaluating whether they were in the latency window. This meant that non-viable servers were considered during the window calculation and would render certain viable servers unviable. ##### [BulkWriteError `writeErrors` property](https://jira.mongodb.org/browse/NODE-2625) [@​vkarpov15](https://togithub.com/vkarpov15) submitted a patch to always include `writeErrors` on a `BulkWriteError`. We have logic to set the `message` of `BulkWriteError` to the message of the first error encountered if there is only one error. Unfortunately, this logic removed the `writeErrors` field when doing that, so users could be faced with an error which conditionally changed shape. ##### [Memory leak in timed out wait queue members](https://jira.mongodb.org/browse/NODE-2413) [@​dead-horse](https://togithub.com/dead-horse) identified a memory leak in the new connection pool where wait queue members which timed out might be left in the queue indefinitely under sufficient load. The fix here was to ensure that all wait queue members are flushed during wait queue processing before evaluating whether there were available sockets to process new requests. ##### [Implicit sessions cleanup improvements](https://jira.mongodb.org/browse/NODE-2630) Once [@​dead-horse](https://togithub.com/dead-horse) was able to patch the connection pool memory leak, they also identified a edge case where implicit sessions could be leaked in a very specific error condition. The logic to release implicit sessions was simplified, preventing this from happening in the future ##### [Unordered bulk writes continue-on-error](https://jira.mongodb.org/browse/NODE-2619) A bug introduced last summer prevented unordered bulk write operations from continuing after the first write error - one of the most important features of being an unordered operation. We now properly support this feature again. ##### [`journal` in connection string is ignored](https://jira.mongodb.org/browse/NODE-2442) [@​nknighter](https://togithub.com/nknighter) filed a report that the `journal` option was ignored when provided via the connection string. The paramater `j` was supported both through the connection string and explicit added to `MongoClient` options, but the official documentation for connection strings support a `journal` option. ##### Documentation Reference: API: Changelog: 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

Bug

  • [NODE-2407] - UnifiedTopology + near read makes application crash with timeout error when one of replica server is down
  • [NODE-2413] - The node process enters an infinite loop at the pool and causes OOM
  • [NODE-2442] - journal=true is ignored in connection string
  • [NODE-2548] - Change streams do not resume from errors
  • [NODE-2565] - Change stream should not check for NonResumableChangeStreamError label
  • [NODE-2619] - Unordered bulk write aborts on first encountered error
  • [NODE-2625] - BulkWriteError should always have a writeErrors field

Task

  • [NODE-2478] - Use white list for change stream resumability
  • [NODE-2598] - Change stream close refactor
  • [NODE-2605] - Refactor shared test helpers to improve usability

Improvement

  • [NODE-2522] - Remove ElectionInProgress (216) from ResumableChangeStreamError
  • [NODE-2571] - Don&#​39;t use admin database for FLE tests
  • [NODE-2630] - Simplify code path for ending implicit sessions in cursors

Renovate configuration

:date: Schedule: "every weekend" (UTC).

:vertical_traffic_light: Automerge: Enabled.

:recycle: Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

:no_bell: Ignore: Close this PR and you won't be reminded about this update again.

This PR has been generated by WhiteSource Renovate. View repository job log here.