feat: add type for failure during deleting dangling referrer index#482
Conversation
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Codecov Report
📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more @@ Coverage Diff @@
## main #482 +/- ##
==========================================
+ Coverage 72.84% 72.92% +0.08%
==========================================
Files 49 49
Lines 4518 4528 +10
==========================================
+ Hits 3291 3302 +11
Misses 919 919
+ Partials 308 307 -1
|
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
|
Is the digest of the manifest that failed to be deleted included in the errro? |
TerryHowe
left a comment
There was a problem hiding this comment.
LGTM
Although please answer Sajay's question. Digest appears to be included to me.
|
I'm struggling to understand why we'd delete content for the user: #479 (comment) |
It implicitly implied in the |
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
There was a problem hiding this comment.
Since we may have more specific errors in the future. It would be better if we can introduce a generic error to avoid error type blow up.
A sample error can be
type ReferrersError struct {
Op string
Subject ocispec.Descriptor
Err error
}Other examples can be found by
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Updated, made it more generic to a |
|
Ignorable is confusing to me. It’s up to the caller to decide that IMHO. |
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Signed-off-by: Billy Zha <jinzha1@microsoft.com>
Resolves #479