increase exec max buffer #6236
Merged
increase exec max buffer #6236
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ruddell
force-pushed
the
increase-exec-max-buffer
branch
from
a9019d7
to
dee92a2
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
As a user's project grows, the build process can fail due to the same issue as in #6059, a specific example is @dancancro's Great Big Example Application. The only way for a developer to work around this is to modify
generator-jhipstercode.I took the default value from
execawhich uses 10MB. NodeJS was going to use 1024*1024 but the PR was closed for inactivity (nodejs/node#11196) and this doesn't seem to be enough (see @dancancro's comment here).