-
Notifications
You must be signed in to change notification settings - Fork 107
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
fix(dedupe): run dedupe only for repositories found at startup #1844
fix(dedupe): run dedupe only for repositories found at startup #1844
Conversation
7da603e
to
61fbbbe
Compare
Codecov Report
@@ Coverage Diff @@
## main #1844 +/- ##
==========================================
- Coverage 92.03% 92.03% -0.01%
==========================================
Files 146 146
Lines 26465 26492 +27
==========================================
+ Hits 24358 24381 +23
- Misses 1556 1559 +3
- Partials 551 552 +1
... and 1 file with indirect coverage changes 📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
Pls fix the conflict. |
Pls fix conflicts. |
61fbbbe
to
60671db
Compare
no need to run dedupe/restore blobs for images being pushed or synced while running dedupe task, they are already deduped/restored inline. Signed-off-by: Petu Eusebiu <[email protected]>
60671db
to
41e9702
Compare
/* at first run get from storage currently found repositories so that we skip the ones that gets synced/uploaded | ||
while this generator runs, there are deduped/restored inline, no need to run dedupe/restore again */ | ||
if len(gen.repos) == 0 { | ||
gen.repos, err = gen.ImgStore.GetRepositories() |
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.
This list could be very large potentially
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.
lgtm
no need to run dedupe/restore blobs for images being pushed or synced while running dedupe task, they are already deduped/restored inline.
What type of PR is this?
bug
Which issue does this PR fix:
#1843
What does this PR do / Why do we need it:
If an issue # is not available please add repro steps and logs showing the issue:
Testing done on this change:
Automation added to e2e:
Will this break upgrades or downgrades?
Does this PR introduce any user-facing change?:
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.