Fix re-running admindb migration failures #205
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #205 +/- ##
==========================================
+ Coverage 34.41% 34.62% +0.20%
==========================================
Files
8000
74 74
Lines 11692 11692
==========================================
+ Hits 4024 4048 +24
+ Misses 7123 7094 -29
- Partials 545 550 +5 |
Make all admindb migration queries re-entrance so re-running migration would not fail. Signed-off-by: Akshay Gaikwad <akgaikwad001@gmail.com>
567685a to
f0ae8a0
Compare
niravparikh05
approved these changes
Apr 28, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Make all admindb migration queries re-entrance so re-running migration would not fail.
Does the PR depend on any other PRs or Issues? If yes, please list them.
None
Checklist
I confirm, that I have...
CONTRIBUTING.mdgo fmt(if applicable)CHANGELOG.md