As a user my sync continues in case it encounters corrupted manifest
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 31
- Forks
- 56
- Avg merge
- 2d 22h
- Merged PRs (30d)
- 22
Description
Is your feature request related to a problem? Please describe.
Right now the sync of the whole repo fails when it encounters at least one corrupted manifest
Describe the solution you'd like
I would like the sync to continue and in the task details record what manifests were skipped.
In case a manifest list is corrupted, whole manifest will be skipped including its all per-arch manifests.
Additional context
This logic should probably be incompatible with mirror=True
Contributor 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.
Research direction
Start by tracing the repository sync path and how task details report skipped manifests. Check how corrupted manifests and manifest lists relate to their per-arch manifests, and define the mirror=True incompatibility. Done means sync continues, skipped manifests are recorded, and a corrupted list skips its complete manifest set.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100