-
Notifications
You must be signed in to change notification settings - Fork 3.8k
Try next mirror in case of non-404 errors, too #5275
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
Conversation
|
Hi @haslersn. Thanks for your PR. I'm waiting for a containerd member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
63be998 to
e3d42f5
Compare
|
Build succeeded.
|
|
Build succeeded.
|
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.
overall LGTM but some minor nits.
remotes/docker/resolver.go
Outdated
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.
nit: lastErr doesn's seems to be the correct name as this actually indicates the first error 🤔
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.
Right, but that seems to already be the case at:
- https://github.com/containerd/containerd/blob/7b9a4ec09280962a801077c15fdf5ff8269c0796/remotes/docker/resolver.go#L286
- https://github.com/containerd/containerd/blob/7b9a4ec09280962a801077c15fdf5ff8269c0796/remotes/docker/resolver.go#L364
- https://github.com/containerd/containerd/blob/7b9a4ec09280962a801077c15fdf5ff8269c0796/remotes/docker/resolver.go#L381
Should I rename it?
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 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.
Done
remotes/docker/resolver.go
Outdated
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.
nit: #4575 (comment) should be commented somewhere.
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.
Done
|
Build succeeded.
|
|
linter is not happy. |
|
Also, please squash the commit. |
|
Build succeeded.
|
@ktock: Done. |
|
Build succeeded.
|
mikebrow
left a comment
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.
LGTM. just had a couple nit questions on the all 404 and no host found cases.
|
@haslersn Please rebase this PR on the latest master. This will solve the CI flakiness. |
|
Build succeeded.
|
|
@dmcgowan PTAL |
Signed-off-by: Sebastian Hasler <sebastian.hasler@gmx.net>
|
I had to manually rebase again because of merge conflict. |
|
Build succeeded.
|
kzys
left a comment
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.
LGTM!
/ok-to-test
|
Can this get merged? |
ktock
left a comment
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.
LGTM
|
Hey gang! We're hanging out waiting with bated breath for this one - it'll solve some significant performance issues for us. I'd appreciate it someone with the right access would merge it - looks as if all the pre-requirements have been met... :) |
|
@dmcgowan How do changes end up in a release? I was hoping this would be in 1.5.3, but it didn't make it... |
|
I have check the code and the merge was NOT include in v1.5.3 👎 |
|
@fuweid We also ran into this issue with Artifactory as our pull through cache. Because we use kOps 1.20 we have to use containerd v1.4.x. |
|
@clifford-sanders Yes. It is possible. I filed the pr #6244. Please wait for next point release. Thanks |
This PR is based on #4575 (comment).
Fixes #4531
Closes #4575