push command - Pushing very large packages is prone to timeouts
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
We can't recommend pushing packages larger than 1GB through Chocolatey, as we haven't really tested that aspect. However some findings have been that choco push will timeout, EVEN when pushing to localhost. Something is making things slow and it's worth investigating any optimizations we could add there.
### Workaround
Setting up a file share on the same directory that an HTTP repo uses for those packages and then pushing to that (possibly copying is what this push means).
Contributor guide
Research direction
Start with the choco push command and reproduce the timeout using a package larger than 1GB, including against localhost. Trace the upload path to identify the source of the slowness; done means an optimization addresses the timeout and the behavior is verified for large packages.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100