maxBuffer should be passed to exec() correctly #67
Conversation
This file contains hidden or 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
Fixes danielgtaylor#44 {env, options} was previously incorrectly expanding to "options: {options: {maxBuffer: ...}}" when being passed to child.process.exec() now it's passed correctly as "options: {maxBuffer: ...}" maxBuffer is still not "infinity" but at least it is being passed correctly now and works for much bigger files solving "stdout maxBuffer exceeded" issue
|
@danielgtaylor can this be merged anytime soon? This would solve issues with previewing larger apiblueprints which is not possible at the moment. |
Yes please. Been anxiously looking forward to the resolution. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Fixes #44
{env, options} was previously incorrectly expanding to "options: {options: {maxBuffer: ...}}" when being passed to child.process.exec()
now it's passed correctly as "options: {maxBuffer: ...}"
maxBuffer is still not "infinity" but at least it is being passed correctly now and works for much bigger files
solving "stdout maxBuffer exceeded" issue