-
Notifications
You must be signed in to change notification settings - Fork 162
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
segfetcher: Stop fetch loop on errors #3306
segfetcher: Stop fetch loop on errors #3306
Conversation
475d214
to
527fcf7
Compare
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.
Reviewed 7 of 7 files at r1.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @lukedirtwalker)
go/lib/infra/modules/segfetcher/fetcher.go, line 145 at r1 (raw file):
// 2 iteration: up & down resolved, core fetched. // 3 iteration: core resolved -> done. // If we need more than that something breaks assumptions.
I'm struggling with this sentence. What breaks which assumption?
d60eb37
to
5da13fe
Compare
If we have an error we should not simply ignore it and continue processing. Instead the fetcher now returns the error immediately. Also * do not continue resolving&fetching when 0 up/down segments are cached * log sciond error code in debug * remove duplicated log about convergence problem * improve returned error when a timeout occurs in QUIC Fixes scionproto#2721 Fixes scionproto#3293 Fixes scionproto#3294 Fixes scionproto#3094
5da13fe
to
268534d
Compare
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.
Reviewed 1 of 1 files at r2.
Reviewable status: complete! all files reviewed, all discussions resolved
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.
Reviewable status: complete! all files reviewed, all discussions resolved
go/lib/infra/modules/segfetcher/fetcher.go, line 145 at r1 (raw file):
Previously, scrye (Sergiu Costea) wrote…
I'm struggling with this sentence. What breaks which assumption?
Done.
If we have an error we should not simply ignore it and continue processing.
Instead the fetcher now returns the error immediately.
Also
Fixes #2721
Fixes #3293
Fixes #3294
Fixes #3094
This change is