Determine cause of auto-exec spawnSync /bin/sh E2BIG
- Dominant language
- TypeScript
- Stars
- 2.5k
- Forks
- 221
- PR merge metrics
- No merged PRs in 30d
Description
**Describe the bug**
Currently my latest build fails on the release step with a E2BIG [error](https://gitlab.com/jdalrymple/gitbeaker/-/jobs/592645060#L125). I've done some research and found this can be due to a few reasons such as to many command argument (doesn't seem like the case here) or texts that are too large.
I feel like it may be the latter, but im unsure of how to debug the issue.
Ill try a temporary work around and comment my [auto-exec](https://github.com/jdalrymple/gitbeaker/blob/master/.autorc.yml) lines, but any suggestions are welcome!
**To Reproduce**
Trying to figure that out right now.
**Expected behavior**
Either mention the troubling file, or not throw an error
**Environment information:**
Gitlab CI & Local (arch linux machine)
**Additional context**
I don't think this is necessarily due to auto. Most likely a spawn problem, just figured it would be helpful to post here for anyone who runs into a similar issue in the future, and to brain storm debugging ideas.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the release step and the auto-exec lines in .autorc.yml, then investigate the linked CI failure and the reported spawnSync /bin/sh E2BIG error. Done means identifying the troubling file or command and either documenting the cause or preventing the release step from failing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, shell, typescript
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 22/100