Fix(2321): No Duplicate CSRs #2460
Merged
Conversation
This file contains 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
|
Fixes #2321 |
ikoenigsknecht
force-pushed
the
fix-2321-duplicate-csr
branch
from
9e0dfa0
to
7b3df49
Compare
|
Merging without review because this was approved on another PR. |
leblowl
pushed a commit
that referenced
this pull request
Apr 29, 2024
* Fix issue of duplicate CRSs being generated * Install LFS with checkout to avoid random errors
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.
The issue seemed to be that we were syncing another user's database before we had loaded ours and the new CSR was being erased, recreated, and the old one would sync, then we'd repeat the process.
Pull Request Checklist
(Optional) Mobile checklist
Please ensure you completed the following checks if you did any changes to the mobile package: