-
Notifications
You must be signed in to change notification settings - Fork 774
schema/manifest_backwards_compatibility_test.go: drop mediatype #552
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
Closed
Closed
Changes from all commits
Commits
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 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
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.
I don't think we want these, because (as we've covered before)
manifest_backwards_compatibility_test.gois about “are we compatible with caught-in-the-wild blobs blobs?” and making local adjustments like this (even to a field which we will be ignoring in the OCI framework) defeats that purpose.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.
For this I am a bit confused, if you can not modify the examples of these tests, these original test data is how to get?
Uh oh!
There was an error while loading. Please reload this page.
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.
It would be nice if all of these blobs had notes on their provenance (like we have here). And for the second example you touch in this PR, we do have those notes. For the other blobs (including the first one you touch in this PR), we're left to trust the initial authors that they found these somewhere and haven't manipulated them too much. So you can add new tests here by capturing new blobs in the wild, and we can drop blobs here if we no longer want to test backwards-compat with an old blob. But we don't want to change the existing blobs by hand.
And all of this is just for
manifest_backwards_compatibility_test.go. In other files you can manipulate as much as you like.