Consistently update segmentTimeoutInMs everywhere
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 1.8k
- PR merge metrics
- No merged PRs in 30d
Description
These were not updated to match the new default:
- https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/src/options.ts#L50-L55
- https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/src/internal/downloadUtils.ts#L267
and README was updated in https://github.com/actions/toolkit/pull/1367 but RELEASES wasn't https://github.com/actions/toolkit/blob/457303960f03375db6f033e214b9f90d79c3fe5c/packages/cache/RELEASES.md?plain=1#L160-L162
Originally posted by @lukaw3d in https://github.com/actions/toolkit/pull/1363#discussion_r1170677923
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 comparing packages/cache/src/options.ts and packages/cache/src/internal/downloadUtils.ts with the new segmentTimeoutInMs default, then check packages/cache/RELEASES.md around the referenced entry. Update the listed code and release documentation so they consistently reflect the new default, and verify the cache package tests or checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 62/100