-
Notifications
You must be signed in to change notification settings - Fork 32
fix: gsoc and pss checks #557
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
base: master
Are you sure you want to change the base?
Conversation
| logger.Infof("gsoc: still missing %d chunks: %v. retrying...", len(missing), missing) | ||
|
|
||
| // Retry missing chunks sequentially to avoid flooding | ||
| for _, i := range missing { |
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.
Should the retry loop check ctx.Done() before each iteration?
Without it, cancellation during retry execution won't be detected until all retries complete.
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.
Yes, there should be a select, with ctx.Done and default directive to pass.
| const numChunks = 10 | ||
| func run(ctx context.Context, uploadClient *bee.Client, listenClient *bee.Client, batches []string, logger logging.Logger, parallel bool, numChunks int) error { | ||
| if numChunks <= 0 { | ||
| numChunks = 3 |
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.
Should show a warning to user that we are changing number of chunks to 3 ?
Why 3 exactly ?
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 think that it is ok to return an error here if chunks number is 0 or negative.
This PR tries to fix GSOC and PSSS checks that fail sometimes