Package specific ability to adjust the execution timeout
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
Some packages already know they take over an hour or more to install. Wouldn't it be nice if the package could request longer periods for install?
Of course it can't be done in automation scripts because by the time those run the value is already locked in stone and counting down. So that leaves either a nuspec enhancement #325 or a special file that could be found in the package
Original conversation with @tcase:
UPDATE: As Chocolatey Gitter chat is now unavailable, I've added a screenshot of the Gitter chat.
Contributor guide
Research direction
Review the proposed nuspec enhancement in #325 and the timeout behavior described in this issue. Determine how a package could request a longer installation period before automation scripts run, then define the scope and completion criteria for the feature.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100