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.
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
feat: grace period for repo errors to prevent aggressive unknown sync state #16085
feat: grace period for repo errors to prevent aggressive unknown sync state #16085
Changes from all commits
ba684eb
b0208aa
36c7a57
2a72af2
b81f8fb
9992f2c
04782a9
ded3e2c
dc56418
fc8a56f
c813525
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Something about introducing an error return value from CompareAppState method signature for the sole purpose of CompareStateRepoError feels unclean. I think it's pretty specialized, and the fact that we only return error in this circumstance is going to get lost over time.
Instead of introducing error for this one purpose, what if we return
nil
, (which is what you are already doing the PR). The caller should interpret a nil return value as indication comparison should be skipped/short-circuted. This way, it doesn't affect the method signature and the semantics seem cleaner.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.
I initially planned to do that, where we returned nil but then decided against it and made it more specific because in the future if the code changes and there's other cases where nil is returned we might forget to update this logic so I chose to go with a specific error for this case.