Buffer() is deprecated warning with a 'length out of range' error followed
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 8.9k
- Forks
- 2.8k
- PR merge metrics
- No merged PRs in 30d
Description
Hey all,
I'm having an issue on my self-hosted windows runner about the Buffer() function in node. The error appears like below and the checkout function stops, preventing the workflow from continuing. Sensitive parts omitted with asteriks as this is a private repository.
`
(node:5708) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
Downloading the archive
Error: Could not create Buffer from response body for https://codeload.github.com/***/***/legacy.zip/cbd6c10880e762dc79c76cb13fbee74ecaf67b2d?token=***: The value of "length" is out of range. It must be >= 0 && <= 2147483647. Received 2501197150
Thought this might be related to code of checkout action repository but still, any ideas on how I can tackle this without waiting for an update?
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 archive download failure on a self-hosted Windows runner and trace the checkout download path where the Buffer is created. Done means checkout can process this archive without the deprecation warning or the length-out-of-range error and the workflow continues.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, node.js, typescript
- Domain
- ci-cd
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100