[24.0 backport] vendor: github.com/docker/distribution v2.8.3 - #46672
Closed
thaJeztah wants to merge 3 commits into
Closed
[24.0 backport] vendor: github.com/docker/distribution v2.8.3#46672thaJeztah wants to merge 3 commits into
thaJeztah wants to merge 3 commits into
Conversation
This utility was setting the content-type header after WriteHeader was called, and the header was not sent because of that. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit a9fcb77) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
The test was depending on the client constructing an error based on the http-status code, and the client not reading the response body if the response was not a JSON response. This fix; - adds the correct content-type headers in the response - includes error-messages in the response - adds additional tests to cover both the plain (non-JSON) and JSON error responses, as well as an empty response. Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit 2c89640) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
- Fix storageDriver gcs not registered in binaries - reference: replace uses of deprecated function SplitHostname - Dont parse errors as JSON unless Content-Type is set to JSON - update to go1.20.8 - Set Content-Type header in registry client ReadFrom - deprecate reference package, migrate to github.com/distribution/reference - digestset: deprecate package in favor of go-digest/digestset - Do not close HTTP request body in HTTP handler full diff: distribution/distribution@v2.8.2...v2.8.3 Signed-off-by: Sebastiaan van Stijn <github@gone.nl> (cherry picked from commit e1d0aac) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>
rumpl
approved these changes
Oct 18, 2023
Member
Author
|
Interesting failures; they look like actual failures, but curious how the failures relate to these changes 🤔 |
Member
Author
|
🙈 😬 found it 😬 looks like I've been a victim of auto-complete in distribution; |
Member
Author
|
closing; there's no plans to do more 24.0.x releases |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
backports of;
fix faulty tests for distribution-client #46555
vendor: github.com/docker/distribution v2.8.3 #46542
relates to Pushing blobs doesn't send content-type #46006
fixes Pushing blobs doesn't send content-type #46006
Diff is different, because the 24.0 branch still uses the deprecated reference package, and doesn't contain;
- Description for the changelog
- A picture of a cute animal (not mandatory but encouraged)