-
Notifications
You must be signed in to change notification settings - Fork 205
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
TAG_INVALID in conformance tests is not present is spec #319
Comments
This was removed from the distribution-spec back in #206. Is this throwing an error for you? It may be useful for UX when interacting with registries that implement the docker registry spec. |
No errors no. I thought I'd bring it up because although they are accepted error codes in the conformance tests, they are not listed in the list of acceptable error codes so I was a bit confused.
Am I nitpicking? |
Mentions `TAG_INVALID` and `MANIFEST_UNVERIFIED` as legacy error codes. Also adjusts error codes' numbering - `code-11` got removed (by accident I assume). Closes opencontainers#319 Signed-off-by: Flavian Missi <[email protected]>
Mentions `TAG_INVALID` and `MANIFEST_UNVERIFIED` as legacy error codes. Also adjusts error codes' numbering - `code-11` was removed by opencontainers#206. Closes opencontainers#319 Signed-off-by: Flavian Missi <[email protected]>
Mentions `TAG_INVALID` and `MANIFEST_UNVERIFIED` as legacy error codes. Also adjusts error codes' numbering - `code-11` was removed by opencontainers#206. Closes opencontainers#319 Signed-off-by: Flavian Missi <[email protected]>
The
TAG_INVALID
error code is currently being checked by the conformance tests, but it's not mentioned in the specification.Should
TAG_INVALID
be added to the spec, or should it be removed from the comformance tests?The text was updated successfully, but these errors were encountered: