greenkeeper[bot]
commented
5 years ago After pinning to 3.2.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
Open greenkeeper[bot] opened 5 years ago
greenkeeper[bot]
commented
5 years ago After pinning to 3.2.7 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.
greenkeeper[bot]
commented
5 years ago dependency mongodb was updated from 3.3.0 to 3.3.1.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago dependency mongodb was updated from 3.3.1 to 3.3.2.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
5 years ago dependency mongodb was updated from 3.3.2 to 3.3.3.Your tests are still failing with this version. Compare changes
The new version differs by 146 commits.
f326744 chore(release): 3.3.34cdb950 Revert "feat(Update): add the ability to specify a pipeline to an update command (#2017)"558d4fb test: simply access to required topology directive8e5391d test: remove deprecated test runner filters0a98aa4 test: don't throw errors in eachAsync in new test runneree15ea0 refactor(monitoring): hoist Server constants out of monitor code8a4de3f test: remove legacy code for no longer existant server bug7b8dcbf test: remove accidentally committed debug code33744f5 test: remove duplicate configuration code3fe378a chore: reenable linting as part of test script6fc750e chore: remove dependency on mongodb-test-runner8ccea97 test(es-next): ensure inventory collection is already createdc5f1558 test: add configuration for evergreenb6f356d test: close => destroy6eb2e16 test: check that servers exist before coercing them into an arrayThere are 146 commits in total.
See the full diff
greenkeeper[bot]
commented
5 years ago dependency mongodb was updated from 3.3.3 to 3.3.4.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.3.4 of the driver
This release primary consists of improvements to the "unified topology". In particular, a regression with interaction between the connection pool and topology could result in servers which "go away" (due to network error, for example) would not return, resulting in a MongoTimeoutError.
The new version differs by 91 commits.
ce60476 chore(release): 3.3.4d126665 fix(topology): report unified topology as nodejs0a22e3f test: allow values other than true for unified filterd38a6b6 refactor(topology): always ensure useUnifiedTopology is present7dc7cb8 test: support only passing options to configuration.newTopology5f6a787 fix(connect): prevent multiple callbacks in error scenariosba123a6 refactor: support a factory type in connect51e8807 doc: introduce documentation about the unified topology design0c1114d refactor(topology): report topology state for helper methodsb493e1b chore(release): 3.3.4-rc0edb1335 fix(topology): set max listeners to infinity for db event relay29e5ef7 test: disable historically flakey test until we can triage the cause63e8fb5 chore: remove evergreen targets that don't run newer node versions06398a3 test: use a universally supported invalid query6475fd9 test: test multiple possible projection error messagesThere are 91 commits in total.
See the full diff
greenkeeper[bot]
commented
5 years ago dependency mongodb was updated from 3.3.4 to 3.3.5.Your tests are still failing with this version. Compare changes
The new version differs by 26 commits.
6930e12 chore(release): 3.3.5b0f83b8 refactor: notify when attempting to use deprecated events/options3b076b3 fix(cursor): call initialize after session support check3471c28 fix(pool): support a drain event for use with unified topologyc24eb91 test: add a color for workload messages to sdam_viz261f1e5 fix(topology): don't drain iteration timers on server selectionb425fe5 refactor(topology): remove extra timers around selection monitoring2d976bd fix(topology): correct logic for checking for sessions support4d2bd6e test: remove use of format in max staleness tests28a944b refactor: minor modification to the workload generator for sdam_viza95347a refactor: use named exports for all SDAM types38d5ed8 test: add support for a simulated read workload to sdam_vizbe0d36e refactor: explicitly disallow selection if topology is closedf07a03f test: add unit tests for selectServers methodf597e52 refactor(monitoring): simplify logic for rescheduling monitoringThere are 26 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.3.5 to 3.4.0.Your tests are still failing with this version. Compare changes
The new version differs by 116 commits.
ff95a2f chore(release): 3.4.0e6ff085 test: only test CSFLE on LTS versions of node13bb49c chore: update mongodb-client-encryption to 1.0.0 in testing8588e57 style: correct linting issues introduced with prettier update0e48300 style: update to newest version of prettierb573fe1 refactor: translate modern tls options to ssl, update documentation806cd62 fix(scram): verify server digest, ensuring mutual authenticationcb107a8 fix: add calculated duration to server as roundTripTimefaab9ad chore: fix name of atlas connectivity testsafb125f fix(srv-poller): always provide a valid number for intervalMS8da416f chore: move srv polling tests to test/unit/sdamb9b5208 refactor(pool): use cancellation token for connection establishment2014b7b feat: support connection establishment cancellation8a07893 refactor: simplify connect, reuse a set for error event namesf3a8093 test: update SDAM spec tests to support multiple phasesThere are 116 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.4.0 to 3.4.1.Your tests are still failing with this version. Compare changes
The new version differs by 5 commits.
bc93598 chore(release): 3.4.1e46a70e fix: always check for network errors during SCRAM conversatione44f553 chore: update google analytics code20800ac fix(bulk): use original indexes as map for current op index3f34e3e doc: update version for doc generationSee the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.4.1 to 3.5.0.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.0 of the driver
This release introduces a modern replacement for the driver's connection pool, available only with the
unified topology. A major effort was made in early 2019 to fully specifiy connection pools for MongoDB
drivers (see: CMAP specification), and this release brings the Node.js driver in line with that
specification.
The new pool supports monitoring for all aspects of its behavior. This allows deep introspection into
the operation of the connection pool, as well as an ability to profile the lifetime of an operation
when used in conjunction with command monitoring.
The Connection class was completely rewritten for the new pool adopting a stream-first mentality. All
wire message processing and compression is handled in a duplex stream called the MessageStream, and
that stream is connected bidirectionally to the underlaying TCP socket. The result is a connection which
gains the general benefit of streams: better performance, less memory pressure, backpressure support. It
also opens the possiblity of supporting non-TCP/UDP streams as a transport for the driver.
The new connection pool has a concept of a "wait queue", which allows operation requests to buffer waiting
for a connection to execute against. There is no timeout by default, but users can now specify a new value
waitQueueTimeoutMS in their connection string or MongoClient options to proactively cancel operations
that have waited too long.
Remember that the new connection pool is only available for the "Unified Topology", so remember to pass
useUnifiedTopology: true to your MongoClient constructor to use it!
Both the legacy and unified SDAM implementations have until now executed monitoring checks as priority
messages in the legacy Pool implementation. This means that monitoring (ismaster) operations were
prioritized over other queued operations, but also means that monitoring could be indefinitely blocked,
in particular during failover or blackhole scenarios. The default socket timeout is null (read: Infinity),
so if the pool was completely saturated with operations, there may be no ability to execute a monitoring
check and determine that the connection to a server was no longer valid. This version of the driver
introduces a new Monitor class which manages its own dedicated monitoring socket to each known
node.
In v3.3.0 of the driver we introduced a new MongoTimeoutError for all errors covered by the server
selection loop, leading to a spike in bug reports with a title similar to Server selection timed out after 30000ms.
Even though the error type itself had an attached reason field, we still feel it was easy to miss why
the selection had failed. As a result we have introduced a new type MongoServerSelectionError which
will use the originating error (reason) for its message, better informing users what caused a
selection error, while still also conveying it is an error in server selection.
The new version differs by 131 commits.
8991285 chore(release): 3.5.0ea56625 chore: waitQueueTimeoutMS is a valid connection string optiona630389 refactor: wait until server destroyed before stopping event relayc04a520 doc: add basic documentation for CMAP event monitoringc01bf50 refactor: don't encode type name into public CMAP event types1aea4de feat: relay all CMAP events to MongoCliented8c9d4 refactor: warn on use of deprecated SDAM events in unified mode7e64df7 test: reduce flakiness of objectid test which checks by time0715a36 doc: add documentation for CMAP events and errors9bd360c feat: include connectionId for APM with new CMAP connection pool9541410 test: ignore ismaster events in change streams spec testsec3d87b test: allow all test files to use custom chai mongodb spec matcher35d0274 fix: report the correct platform in client metadatac528a66 Revert "fix: remove servers with me mismatch in updateRsFromPrimary"903208f Revert "test: include auth information in generated test connection string"There are 131 commits in total.
See the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.0 to 3.5.1.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.2 to 3.5.3.Your tests are still failing with this version. Compare changes
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.3 to 3.5.4.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.4 of the driver
hasNext when piping a cursorPierre Mallet and @Sintendo helped identify a regression with our cursors which did not
properly rewind a cursor when hasNext was called before the cursor was piped.
A change introduced in v3.5.3 converted the server selection loop from a loop with timers
to a queue of callbacks. A subtle bug was introduced to the code to process the quere where
the upper bound of a for loop was using a dynamically decreasing length, leading to some
operations being ignored, and ultimately timing out. Many thanks to Frederic Maillasson,
@paulrobinson, and @adityapatadia for helping uncover this issue
User @millerick submitted a PR short circuiting the background task for ensuring a minimum
pool size if no minimum size was set.
The new version differs by 15 commits.
582d3e2 chore(release): 3.5.4e08b358 chore: disable test using CodeWScope with a $where clause3dd726c chore: upate EVG macos runs to use 10.14 boxes494dffb fix(topology): enter STATE_CLOSING before draining waitQueuebf701d6 fix(topology): ensure selection wait queue is always processed361bc1e refactor: remove SKIP_SESSION aspectf6a8ceb refactor: use maybePromise for all MongoClient fake operations6f71507 chore: move sdam spec unit tests from unit/core to unit/sdama1e0849 fix(sdam): use ObjectId comparison to track maxElectionId2d1b713 fix(cmap): don't run min connection thread if no minimum specifiedf8694f5 refactor: remove nextObject helper, inline code in cusror classbb359a1 fix: don't consume first document when calling hasNext on cursorc56ff72 test: add test for hasNext not consuming first document in stream76333fc refactor: use maybePromise instead of fake operationsac9e4c9 feat: add utility helper for returning promises or using callbacksSee the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.4 to 3.5.5.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.5 of the driver
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.
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.
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.
@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!
The new version differs by 11 commits.
d7ac176 chore(release): 3.5.5f69f51c fix: multiple concurrent attempts to process the queue may failcde11ec fix: pass optional promise lib to maybePromise0c36a32 NODE-2474: update equal server description (#2260)6b3b64d test: ensure mock server is setup before continuing with tests6238c84 fix: correctly use template string for connection string error message44097c2 test: use a reduced minHeartbeatFrequencyMS for spec test runneref04d00 fix(cursor): hasNext consumes documents on cursor with limitb72fefe docs: update community links to use MongoDB Community forumse7dd608 docs: fix typo and formatting of bulletted lists3ddaa3e fix: don't depend on private node api for Timeout wrapperSee the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.5 to 3.5.6.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.6 of the driver
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.
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 arrayA 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.
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!
The new version differs by 14 commits.
08e89c0 chore(release): 3.5.6e43d39a chore: require bson 1.1.4 or highera6f6da0 test: wait for mock server creation before using it611be8d fix: only mark server session dirty if the client session is alive7403e31 docs: Fix typo in Collection#find paramf9e786a fix: always return empty array for selection on unknown topologyd6f3001 Revert "fix: createCollection only uses listCollections in strict mode"a50611b fix: single readPreferenceTags should be parsed as an arrayd368f12 fix: createCollection only uses listCollections in strict mode153646c fix: don't throw if withTransaction() callback rejects with a null reason7778977 chore: remove superfluous build variantsa0b1c5a chore: remove exotic build configurations1c4cf6c fix: polyfill for util.promisify704f30a fix(cursor): transforms should only be applied once to documentsSee the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.6 to 3.5.7.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.7 of the driver
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.
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!
The new version differs by 12 commits.
6eb6d6c chore(release): 3.5.77f1cf35 refactor(ChangeStream): use maybePromise for next/hasNext8851a28 docs: fix event names in gridFS tutorial8a69ed6 chore: update snappy version to fix issue with node v461aaa3d doc: document options supported by the unified topologyf778ef5 test: reduce flakiness of socket timeout test3d05a6d fix: limit growth of server sessions through lazy acquisition56a1b8a fix: remove circular dependency warnings on node 1484d2354 test: temporarily skip sharded transactions tests0b6f813 chore: update package lock to depend on latest bson version0665a02 test: remove replicaset topology from reIndex testsd8bbb55 test: lint the driver in a single evergreen taskSee the full diff
greenkeeper[bot]
commented
4 years ago dependency mongodb was updated from 3.5.7 to 3.5.8.Your tests are still failing with this version. Compare changes
The MongoDB Node.js team is pleased to announce version 3.5.8 of the driver
@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.
writeErrors property@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.
@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.
Once @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
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@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.
Reference: http://mongodb.github.io/node-mongodb-native/3.5/
API: http://mongodb.github.io/node-mongodb-native/3.5/api/
Changelog: https://github.com/mongodb/node-mongodb-native/blob/3.5/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!
The new version differs by 14 commits.
9c4288c chore(release): 3.5.85c6fda1 fix: ensure implicit sessions are ended consistently0394f9d fix: always clear cancelled wait queue members during processing58b4f94 fix: always include writeErrors on a BulkWriteError instance6cee96b fix: unordered bulk write should attempt to execute all batches4faf9f5 fix: filter servers before applying reducers5ecf18e fix(ChangeStream): should resume from errors when iterating7fad15a test: improve shared helpers246669f fix: honor journal=true in connection string (#2359)1e3b4c9 refactor(ChangeStream): use maybePromise for close, improve tests5e7197a test: ignore error for missing killAllSessions on legacy versions4f987f1 refactor: don't use admin database in CSFLE testsa9d3965 fix(ChangeStream): whitelist resumable errors (#2337)922c3ab test: use a different conflicting option for index error validationSee the full diff
The dependency mongodb was updated from
3.2.7to3.3.0.🚨 View failing branch.
This version is covered by your current version range and after updating it in your project the build failed.
mongodb is a direct dependency of this project, and it is very likely causing it to break. If other packages depend on yours, this update is probably also breaking those in turn.
Status Details
- ❌ **continuous-integration/travis-ci/push:** The Travis CI build is in progress ([Details](https://travis-ci.org/duyluonglc/lucid-mongo/builds/571366048?utm_source=github_status&utm_medium=notification)). - ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/duyluonglc/lucid-mongo/builds/26668146)).Commits
The new version differs by 1878 commits ahead by 1878, behind by 7.
8b3c3b0chore(release): 3.3.00d2018cdocs(AutoEncryption): adds documentation for extraOptions3ecda98docs(autoEncryption): document that autoEncryption is in beta814a4ccchore(useUnifiedTopology): add deprecation warning for useUnifiedTopologyb7308dbtest: disable some failing tests for later investigationb23e606test(transactions): disable invalid pinning test82a7a6echore(travis): add 4.2 testing to travis392f5a6fix(topology): add new error for retryWrites on MMAPv12ef8f2cchore(ci): update evergreen config to test Ubuntu 18.04 on mongodb >= 4.2ae729f8refactor(change-stream): useAggregateOperationfor stream cursor831968drefactor(cursor): return operation readPreference with priority1ffe9b7refactor(client): provide default namespace and read preference778928frefactor(command): support full response as command op option6acef6drefactor(find): useFindOperationfor finds0f88582refactor(cursor): modernize and deduplicate cursor classesThere are 250 commits in total.
See the full diff
FAQ and help
There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).Your Greenkeeper Bot :palm_tree: