Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Specify max buffer of execFile #72

Open
pd4d10 opened this issue Oct 17, 2019 · 2 comments · May be fixed by #91
Open

Specify max buffer of execFile #72

pd4d10 opened this issue Oct 17, 2019 · 2 comments · May be fixed by #91
Assignees

Comments

@pd4d10
Copy link

pd4d10 commented Oct 17, 2019

If the stdout exceeds the default max buffer size(1024 * 1024), it would throw an error:

UnhandledPromiseRejectionWarning: RangeError [ERR_CHILD_PROCESS_STDIO_MAXBUFFER]: stdout maxBuffer length exceeded

Reference: https://nodejs.org/api/child_process.html#child_process_maxbuffer_and_unicode

Seems it is necessary to add an option to specify it.

@kessler kessler assigned kessler and M1cr0M1nd and unassigned M1cr0M1nd and kessler Sep 2, 2021
@NightFurySL2001
Copy link

Is there any fix for this yet? Logging some of the paths will easily exceed the max buffer size.

@6ixfalls
Copy link

6ixfalls commented Oct 7, 2021

Had to manually edit this for my use case, as the buffer is larger than the default setting. Would be great if this could be done, as it's not that complex, just another argument that needs to be passed into childProcess.execFile.

@6ixfalls 6ixfalls linked a pull request Oct 7, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants