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
Fixes Issue #610 #611
Fixes Issue #610 #611
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the Pull Request and the detailed information about your findings and tests. I will approve and merge this PR.
I've ran into some failed tests on both test and test:legacy so for this reason I am going to try and get one of our maintainers (Lino) to take a look at the PR and approve. But thank you for the PR, we are working on it. |
Sounds good. Let me know if I can help! Will the github action run to test this? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will be reviewing this PR this week. We may make changes to or replace this PR with something else that works the same. Either way, we will resolve this issue.
Quick update: I have been using the code in this pull request for about a month now and have not found any new issues! 😊 |
Thanks for the update @zachlankton!! I'll see what we can do about getting this into the next release. I appreciate the contribution! |
@zachlankton We've updated the testing workflow to include PRs from branches in forks. Could you amend your last commit (just change a single character or something) to trigger the tests? |
Codecov Report
@@ Coverage Diff @@
## master #611 +/- ##
==========================================
- Coverage 95.21% 95.00% -0.22%
==========================================
Files 93 93
Lines 2487 2580 +93
Branches 566 574 +8
==========================================
+ Hits 2368 2451 +83
- Misses 111 122 +11
+ Partials 8 7 -1
Continue to review full report at Codecov.
|
Looks like the tests are passing, but code coverage is failing for files and lines of code that this PR did not touch. Looks like the same thing is happening in PR #614 |
Actually, just noticed codecov is comparing this pull request to an old commit from August — 1fb8ced |
I believe this is ok for now, I'll touch base with the team tomorrow. Thanks so much @zachlankton! |
Hey @zachlankton just a quick update on this: we're planning on including it in our next release (sometime next week I believe)! Thanks again for being a part of our growing community. Cheers! |
This pull request fixes issue #610 as well as passes all legacy and non legacy tests (without the
OTTOMAN_LEGACY_TEST=1
set).Intermittently there would be
LCB_ERR_KEYSPACE_NOT_FOUND
when creating new collections and indexes. This would happen because sometimes theensureCollections
would return before the collections were actually ready. Additionally sometimes there would be QueryPlanning Failures
when running on freshly created models because theensureIndexes
would not return theindexOnlinePromise
unlessindexReadyHooks
were defined.The changes in this pull request refactor some logic in the
ensureCollections
andensureIndexes
functions. It now guarantees that the collections and the indexes will be ready as described in the documentation.