-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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: added retry on files sync error #9261
Merged
ericzzzzzzz
merged 3 commits into
GoogleContainerTools:main
from
idsulik:feature/added-retry-on-sync-error
Jul 12, 2024
Merged
Changes from all commits
Commits
Show all changes
3 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
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.
Did you leave this here intentionally while working on this feature? Were you planning to incorporate any changes before committing?
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.
No, not in this PR, I left it in case if anyone wants to do it, maybe I'll do it by myself, but not now
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'd suggest to implement configurable re-try for sync and default it to
0
-- not re-try to keep the user experience the same as before, if we want to have a sync retry, but I am still not convinced that we need this.While
// todo
comments might seem like helpful reminders, they often create more problems than they solve:Limited Visibility
: Only those who stumble upon the specific code section see the comment, potentially leaving others unaware of the task.Unclear Ownership and Status
: There's no indication of who's responsible for the task, whether it's assigned, in progress, or forgotten.Lack of Discussion
: Meaningful conversations are difficult without a dedicated issue or pull request, hindering collaboration.Prioritization Challenges
: Maintainers struggle to assess the urgency and importance of tasks scattered throughout the codebase.Ambiguity in Pull Requests
: It's unclear if // todo marks unfinished work or instructions for future changes, causing confusion during reviews.These issues often lead to // todo items being overlooked or forgotten.
A more effective approach is to create an issue for each task: