Keep and Untagged seem to compound, is that intentional?
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by reproducing the described purge scenario with --keep 10 --untagged and --ago 0d against a repository containing tags sharing one manifest, then trace the purge flow that performs untagging and removal. Confirm the intended semantics with the issue discussion; done means the behavior is documented or corrected and covered by a regression test for the expected tag and manifest counts.
Written by the indexing model from the issue text.
Description
Describe the bug
First of all, not sure if this is a bug. But let me describe a scenario.
When you have a repository with 50 tags all linked to a single manifest (so 50 manifests) and you run purge on this 1 repository with "--keep 10 --untagged" and for simplicity lets say you set "--ago 0d".
Then purge would first untag 40 manifests, leaving you with 10 still tagged.
And after that, it would remove 30 of the 40 untagged manifests.
The end result being:
10 tags
20 manifests
To Reproduce
See description
Expected behavior
With the example above in mind, I somehow expected to end up with 10 tags and 10 manifests.
I'm just wondering if how it currently works is intentional or a byproduct of adding (the keep) functionality where this is a (happy) accident.
Any relevant environment information
- OS: Windows
- Version (acr-cli) 0.19
- Dominant language
- Go
- Stars
- 71
- Forks
- 52
- Avg merge
- 8d 10h
- Merged PRs (30d)
- 4
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/acr-cli
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 35/100
Azure/acr-cli#670 · 2 reactions ·
Maintainers usually reply within 1 day
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 52/100
Azure/acr-cli#621 · 2 comments ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Azure/acr-cli#611 · 2 comments ·
Maintainers usually reply within 1 day
Similar issues
-
`renderLinkedIssues` overshoots its byte budget: unresolved and omitted lists are never boundedOpenagent-butler-finding agent-research-recommend bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
jordansmall/spindrift#4614 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
weaviate/weaviate-go-client#485 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 85/100
litmuschaos/litmus#5641 ·
Maintainers usually reply within 6 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 79/100
Maintainers usually reply within 1 day