-
-
Notifications
You must be signed in to change notification settings - Fork 121
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
ENOBUFS error when the to be committed files exceed 1MB #27
Comments
I have increased the buffer to 100MB and it works. You can check this commit on my fork |
Hi, thanks for the issue! It seems like a good idea: would you mind opening a PR for this? Also, maybe it works just fine with something less, 100MB seems a little overkill 😂 |
Yes, I will open a PR soon. My docs folder is already 10MB in size. Do you think 20MB is is suitable? |
Well, the buffer size is the size of the console output, which should be linked to the diff... |
Looking at this with a fresh mind. I think there is a better approach. Instead of increasing the buffer we can simply resolve the root cause, which is 'making sure the output does not exceed 1MB'. You stated I tested this on my fork and it works. Check PR #28 |
Perfect! This seems like a waaaaaay better solution |
The fix has been published in a new release! you can get the fixed version using |
@all-contributors please add @RobinWijnant for bug and code |
This project's configuration file has malformed JSON: .all-contributorsrc. Error:: Unexpected token ] in JSON at position 1752 |
@all-contributors please add @RobinWijnant for bug and code |
I've put up a pull request to add @RobinWijnant! 🎉 |
I am trying to commit the docs folder generated in a previous step. This throws the following error after 1s on
execFileSync
. I found that ENOBUFS is thrown when the maxBuffer (1MB by default) gets exceeded.This happens to be the case here. When only committing a single HTML file from the docs folder, the action succeeds as expected.
Possible solution
The buffer size can be specified as an option with
execFileSync
. More in the docs of Node.js. Setting an increasedmaxBuffer
might solve the issue.My workflow yml:
The text was updated successfully, but these errors were encountered: