Test installation of very large lazily-synced package
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 49
- Forks
- 88
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 31
Description
Original Pulp Redmine Issue: https://pulp.plan.io/issues/7402
Some of the largest packages, such as TensorFlow, can be as large as 340 megabytes in size [0]. Some may even be larger.
If such packages are lazily-synced, and a user tries to install them from Pulp, we should ensure that any delays incurred by Pulp in the process of downloading these packages in the background does not interfere with the operation of the client making the request to Pulp.
A manual test would be acceptable, but an automated test that is not part of the standard CI suite would be better.
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
No source file or test entry point is named. Start by locating the Pulp Python plugin's existing lazy-sync and installation tests, then exercise a TensorFlow-sized package from PyPI while it downloads in the background. Done means confirming that the client installation request is not disrupted; a manual test or an automated test outside standard CI is acceptable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100