artifacts of content requested through 'Range' requests are not saved
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 598
- Forks
- 168
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 86
Description
Version
3.20.0 but effects many versions before it.
Describe the bug
"On-Demand" content requested with a Range header does not have it's artifact saved in Pulp.
To Reproduce
Sync a repository with remote that has 'on_demand' download policy.
Publish it.
Create a Distribution.
Make a request with 'Range' header for a part of a file that is available at the distribution's base_url.
Observe that no new artifacts were created.
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 the on-demand sync, publish, distribution, and ranged-file request described in the issue, then trace where the request is handled and artifacts are persisted. Done means a Range request for previously unavailable content creates and saves the artifact in Pulp; the issue does not name a file or test to begin with.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100