You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug was reported by Wei. I have tested offline with Wei and the bug can be fixed with this pr.
Scenario: image manifest A has a subject, which is artifact manifest B. When pushing A to the registry, the registry returns "subject not found" while B already exists in the repository.
Issues and how to fix them:
According to the distribution spec, subject existence check is not needed and thus should be removed.
Currently, subject is included in the References() of the manifest. All elements of References() are checked for existence in a loop and it's hard to tell which element is the subject. As subject validation is different from the validation of layers, blobs and configs (all included in References()), it's better to move subject out of References().
The text was updated successfully, but these errors were encountered:
wangxiaoxuan273
changed the title
Need to look into Wei's reported bug.
bug: Subject existence check fails when only checking blobstore
Jan 5, 2023
wangxiaoxuan273
changed the title
bug: Subject existence check fails when only checking blobstore
bug: Subject existence check fails when checked with References()
Jan 5, 2023
This bug was reported by Wei. I have tested offline with Wei and the bug can be fixed with this pr.
Scenario: image manifest A has a subject, which is artifact manifest B. When pushing A to the registry, the registry returns "subject not found" while B already exists in the repository.
Issues and how to fix them:
References()
of the manifest. All elements ofReferences()
are checked for existence in a loop and it's hard to tell which element is the subject. As subject validation is different from the validation of layers, blobs and configs (all included inReferences()
), it's better to move subject out ofReferences()
.The text was updated successfully, but these errors were encountered: