Skip to content
This repository was archived by the owner on May 17, 2021. It is now read-only.

Conversation

@imlucas
Copy link
Contributor

@imlucas imlucas commented Mar 14, 2016

cc @durran


This change is Review on Reviewable

@mention-bot
Copy link

By analyzing the blame information on this pull request, we identified @durran to be a potential reviewer

durran added a commit that referenced this pull request Mar 15, 2016
Unpin Kerberos so we don't have multiple versions in Compass
@durran durran merged commit 014aee6 into master Mar 15, 2016
@durran durran deleted the unpin-kerberos branch March 15, 2016 17:03
imlucas added a commit that referenced this pull request Nov 12, 2019
These were breaking on update because of info leakage from driver.

1. Connectivity is tested with `mongodb-connection-model#test()` not via a connect() call because a test should use different timeout values than a connection which will be used more than once. In the case of this test, the selection timeout in the driver is 30000ms which caused this test to fail with `exceeded test timout of 2000`.

2. Retryable reads and writes are now supported by the driver which invalidates the state the disconnect() test relied upon, resulting in a `Topology Destroyed` errror for subsequent calls to the client once closed. Like #1 above, after 30000ms, the `count()` would eventually error but full disconnect() behavior is tested in many other code paths.
imlucas added a commit that referenced this pull request Nov 12, 2019
* chore: update to `[email protected]`

* chore: remove extraneous mongodb-core dependency

* driver: Update to [email protected]

* fix: remove old smoke tests

These were breaking on update because of info leakage from driver.

1. Connectivity is tested with `mongodb-connection-model#test()` not via a connect() call because a test should use different timeout values than a connection which will be used more than once. In the case of this test, the selection timeout in the driver is 30000ms which caused this test to fail with `exceeded test timout of 2000`.

2. Retryable reads and writes are now supported by the driver which invalidates the state the disconnect() test relied upon, resulting in a `Topology Destroyed` errror for subsequent calls to the client once closed. Like #1 above, after 30000ms, the `count()` would eventually error but full disconnect() behavior is tested in many other code paths.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants