Assets left in cache location in the event of a cancelled sync task
Open
Nobody has claimed this yet.
Issue
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Author: wibbit (wibbit)
Redmine Issue: 7636, https://pulp.plan.io/issues/7636
While syncing a ~30GB rpm repository, the task was stopped partway through the process.
This left all of the downloaded assets behind in the WORKING_DIRECTORY, this particular issue is compounded by #7635.
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 reproducing a cancelled sync task against a large RPM repository and inspect how downloaded assets are handled in WORKING_DIRECTORY. The work is done when cancelling the sync no longer leaves its downloaded assets behind; also check the interaction with issue #7635.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100