Update dependency mongodb to v3.5.7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
mongodb	dependencies	minor	3.4.1 -> 3.5.7

---

Release Notes

mongodb/node-mongodb-native

v3.5.7

Compare Source

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

Release Highlights

Warning: Accessing non-existent property 'count' of module exports inside circular dependency

Work earlier this year left some dead code in our operations code, resulting in this warning message reported by multiple users. While we still have a few cycles in our codebase yet, this will quiet Node.js 14's circular dependency warnings.

Sessions are only acquired when operations are executed

Drivers use an implicit session for all operations where an explicit session is not provided. A subtle bug was introduced when session support was implemented where implicit sessions were created and assigned to operations even if they were about to sit in a queue waiting for execution. This results in the driver creating many sessions rather than reusing pooled ones. The fix is to ensure a session is only checked out of the pool when the operation is about to be written to a server.

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

Release Notes

Bug

• [NODE-2536] - Circular dependency in Node.js 14 nightly
• [NODE-2552] - Server session creation grows unbounded with every operation call

Improvement

• [NODE-2534] - Document options supported by the unified topology
• [NODE-2560] - Make &#​39;reIndex&#​39; a standalone-only command

v3.5.6

Compare Source

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

Release Highlights

Regression in map when cursor used as a stream

@​dobesv helped identify a regression where a map function would be applied twice
if defined on a cursor, and that cursor was used to stream data.

TypeError: Cannot read property 'code' of undefined

User @​linus-hologram originally reported an issue with a TypeError when the lambda
passed to the withTransaction helper rejected with a null value. @​vkarpov15
submitted the fix.

readPreferenceTags interpreted as an array

A bug was fixed where readPreferenceTags with a single value in the connection
string was not properly interpreted as an array of tags. This prevented the
Use Analytics Nodes to Isolate Workload guidance from working
correctly.

Cannot set property 'isDirty' of null

User @​sean-daley reported seeing this in an AWS Lambda environment, but has proven to
be somewhat of a heisenbug. We are rolling out a fix here that ensures sessions
(implicit or not) are not used after they have been explicitly ended.

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

Release Notes

Bug

• [NODE-2503] - Cursor ReadStream applies map function twice
• [NODE-2515] - TypeError when transaction is rejected with empty reason
• [NODE-2541] - readPreferenceTags are not interpreted as an array
• [NODE-2545] - Cannot set property &#​39;isDirty&#​39; of null
• [NODE-2549] - Unknown topology should return empty array for server selection with read preference

v3.5.5

Compare Source

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

Release Highlights

Regression in hasNext when using a cursor with a limit

@​peterbroadhurst helped point out a regression introduced in v3.5.4 where using hasNext
on a cusor with a limit would not return the full set of results.

Ignored topology updates cause servers to fall out of latency window

A change introduced across all MongoDB drivers, and in particular v3.5.0 of the Node.js
driver, attempted to prevent needless duplicate topologyDescriptionChanged topology events
by introducing a ServerDescription equality operator. Since equality does not take the
lastUpdateTime and lastWriteDate fields of an ismaster into account, the driver could
eventually consider servers non-suitable for server selection, since they would fall out
of the latency window.
All updates are considered viable for topology updates now, and only event emission is
gated by ServerDescription equality.

Memory leaks with Node.js v12+

The legacy topology types (in particular if you were connected to a replic set) used a
custom Timeout class to wrap a timer. Unfortunately, the class depended on an undocumented,
private variable _called, which was removed in Node.js v12. This would lead to the driver
thinking the timeout never occurred, and therefore never releasing the object for garbage
collection. We recommend users of the legacy topology types immediately update to this
version of the driver, or use the Unified Topology which is unaffected by this bug.

TypeError: Cannot read property 'Symbol(cancelled)' of undefined

@​erfanium and @​Paic helped us identify an issue in rare failover events where multiple
requests to process the server selection queue would result in an attempted property
access of an undefined variable.

promiseLibrary not respected by newly introduced maybePromise helper

@​tobyealden pointed out that an internal refactor to use a helper to optionally
return a Promise for top level API methods was not, in fact, using a custom
promise library if one was provided!

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

Release Notes

Bug

• [NODE-2460] - Memory Leak with ReplSet and NodeJS v12
• [NODE-2472] - TypeError on server available with useUnifiedTopology: true
• [NODE-2474] - Server_Description update with lastUpdateTime / lastWriteDate fields is ignored in topology
• [NODE-2480] - TypeError after reconnecting
• [NODE-2483] - Regression using hasNext on cursor with limit
• [NODE-2490] - promiseLibrary option is not honoured

v3.5.4

Compare Source

Bug Fixes

• cmap: don't run min connection thread if no minimum specified (2d1b713)
• sdam: use ObjectId comparison to track maxElectionId (a1e0849)
• topology: ensure selection wait queue is always processed (bf701d6)
• topology: enter STATE_CLOSING before draining waitQueue (494dffb)
• don't consume first document when calling hasNext on cursor (bb359a1)

Features

• add utility helper for returning promises or using callbacks (ac9e4c9)

v3.5.3

Compare Source

Bug Fixes

• message-stream: support multiple inbound message packets (8388443)
• server: non-timeout network errors transition to Unknown state (fa4b01b)

Features

• connection: support exhaust behavior at the transport level (9ccf268)

v3.5.2

Compare Source

Bug Fixes

• properly handle err messages in MongoDB 2.6 servers (0f4ab38)
• topology: always emit SDAM unrecoverable errors (57f158f)

v3.5.1

Compare Source

Bug Fixes

• cmap: accept all node TLS options as pool options (5995d1d)
• cmap: error wait queue members on failed connection creation (d13b153)
• connect: listen to secureConnect for tls connections (f8bdb8d)
• transactions: use options helper to resolve read preference (9698a76)
• uri_parser: TLS uri variants imply ssl=true (c8d182e)

v3.5.0

Compare Source

Bug Fixes

• copy ssl option to pool connection options (563ced6)
• destroy connections marked as closed on checkIn / checkOut (2bd17a6)
• ensure sync errors are thrown, and don't callback twice (cca5b49)
• ignore connection errors during pool destruction (b8805dc)
• not all message payloads are arrays of Buffer (e4df5f4)
• recover on network error during initial connect (a13dc68)
• remove servers with me mismatch in updateRsFromPrimary (95a772e)
• report the correct platform in client metadata (35d0274)
• reschedule monitoring before emitting heartbeat events (7fcbeb5)
• socket timeout for handshake should be connectTimeoutMS (c83af9a)
• timed out streams should be destroyed on timeout event (5319ff9)
• use remote address for stream identifier (f13c20b)
• used weighted RTT calculation for server selection (d446be5)
• execute-operation: don't swallow synchronous errors (0a2d4e9)
• gridfs: make a copy of chunk before writing to server (b4ec5b8)

Features

• add a withConnection helper to the connection pool (d59dced)
• include connectionId for APM with new CMAP connection pool (9bd360c)
• integrate CMAP connection pool into unified topology (9dd3939)
• introduce MongoServerSelectionError (0cf7ec9)
• introduce a class for tracking stream specific attributes (f6bf82c)
• introduce a new Monitor type for server monitoring (2bfe2a1)
• relay all CMAP events to MongoClient (1aea4de)
• support socket timeouts on a per-connection level (93e8ad0)

3.4.1 (2019-12-19)

Bug Fixes

• bulk: use original indexes as map for current op index (20800ac)
• always check for network errors during SCRAM conversation (e46a70e)

---

Renovate configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻️ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

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

---

• If you want to rebase/retry this PR, check this box

---

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