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

Update Mongodb client to 2.2.4 #2329

Merged
merged 5 commits into from
Jul 20, 2016
Merged

Update Mongodb client to 2.2.4 #2329

merged 5 commits into from
Jul 20, 2016

Conversation

flovilmart
Copy link
Contributor

We needed to tweak a bit the test so the next beforeEach won't crash trying to delete all data with a broken connection as the new mongo client will fail.

@drew-gross
Copy link
Contributor

We also need to add a test to catch the bug/fix that was introduced in 2.1.19 which was what caused all those issue back then.

@flovilmart
Copy link
Contributor Author

flovilmart commented Jul 19, 2016

@drew-gross you remember what the problem was? Reconnection issues?

@yuzeh
Copy link
Contributor

yuzeh commented Jul 19, 2016

It might have been related to this? https://github.com/christkv/mongodb-core/issues/112

@flovilmart
Copy link
Contributor Author

YEs seems like it, I need to drill down further to make sure our mongo adapter properly reconnects after losing the connection.

@ghost
Copy link

ghost commented Jul 19, 2016

@flovilmart updated the pull request.

@flovilmart
Copy link
Contributor Author

Tested with very short socketTimoutMS values and it's magic.

- Just because this way we can let the adapter an opportunity to yield a new error....
OR A SUCCESS
@ghost
Copy link

ghost commented Jul 19, 2016

@flovilmart updated the pull request.

@@ -65,6 +65,8 @@ describe('server', () => {
expect(response.statusCode).toEqual(500);
expect(body.code).toEqual(1);
expect(body.message).toEqual('Internal server error.');
// Reconfigure with null so the next beforeEach don't fail trying to delete
reconfigureServer({ databaseAdapter: null });
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Use reconfigureServer({ databaseAdapter: null }).then(done); please, reconfigureServer returns a promise.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK!

@ghost
Copy link

ghost commented Jul 19, 2016

@flovilmart updated the pull request.

@ghost
Copy link

ghost commented Jul 20, 2016

@flovilmart updated the pull request.

@flovilmart flovilmart closed this Jul 20, 2016
@flovilmart flovilmart reopened this Jul 20, 2016
@flovilmart flovilmart merged commit dfac972 into master Jul 20, 2016
@flovilmart flovilmart deleted the mongodb-client-2.2.4 branch July 20, 2016 01:40
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Mar 15, 2017
* chore(package): update mongodb to version 2.2.4

https://greenkeeper.io/

* fix for mongo 2.2.4

* Delete schema promise on error...

- Just because this way we can let the adapter an opportunity to yield a new error....
OR A SUCCESS

* Fixes test

* Restore fix
rsouzas pushed a commit to back4app/parse-server that referenced this pull request Mar 16, 2017
* chore(package): update mongodb to version 2.2.4

https://greenkeeper.io/

* fix for mongo 2.2.4

* Delete schema promise on error...

- Just because this way we can let the adapter an opportunity to yield a new error....
OR A SUCCESS

* Fixes test

* Restore fix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants