-
Notifications
You must be signed in to change notification settings - Fork 12
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
Error: stdout maxBuffer exceeded #1
Comments
Are you sure xml2js is involved? It does not work with stdout directly. The solution is probably to chunk the output at shared.js:19. I will look into this. |
Pretty much sure - in check.js you run "svn log --non-interactive I guess chunking won't help - xml2js tries to slurp entire XML before On Wed, Aug 17, 2016 at 6:33 PM, RoboPhred [email protected] wrote:
Sincerely yours, Alexander Kuznetsov |
Can we merge that fixed? For now the only workaround is to use the fork of the fork who actually got published to docker hub |
Sorry about dropping this. I no longer work with concourse (or svn for that matter) and do not have any means of testing this. I need to get around to deprecating this repo and pointing visitors to a maintained version. Would you recommend that fork as the best alternative? |
Hi,
tried to hook up to a repo with 4049 log entries, the resource had failed with "Error: stdout maxBuffer exceeded". I dug a bit deeper, there is no quick fix - xml2js does not do stream parsing.
Sounds like a way to go is plain text output from
svn log', then split by
|', then disseminate values into properties.That would also weed of one dependency.
The text was updated successfully, but these errors were encountered: