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

Error: stdout maxBuffer exceeded #1

Open
acca301 opened this issue Aug 17, 2016 · 4 comments · May be fixed by #3
Open

Error: stdout maxBuffer exceeded #1

acca301 opened this issue Aug 17, 2016 · 4 comments · May be fixed by #3
Assignees

Comments

@acca301
Copy link

acca301 commented Aug 17, 2016

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.

@RoboPhred
Copy link
Owner

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.

@RoboPhred RoboPhred self-assigned this Aug 17, 2016
@acca301
Copy link
Author

acca301 commented Aug 19, 2016

Pretty much sure - in check.js you run "svn log --non-interactive
--no-auth-cache --xml" and do
parser.parseString(stdout, (err, info). parser is "new xml2js.Parser"

I guess chunking won't help - xml2js tries to slurp entire XML before
spitting out anything.

On Wed, Aug 17, 2016 at 6:33 PM, RoboPhred [email protected] wrote:

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

console.log(prettyJson(result));
.
I will look into this.


You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#1 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF6Whsgry8AZEOnbq7RUw8gjkNl7LanQks5qg4xUgaJpZM4Jmz6a
.

Sincerely yours, Alexander Kuznetsov

wfranzini pushed a commit to wfranzini/concourse-svn-resource that referenced this issue Apr 7, 2017
@wfranzini wfranzini linked a pull request Apr 7, 2017 that will close this issue
@daniellavoie
Copy link

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

https://github.com/mattwhittingham/concourse-svn-resource

@RoboPhred
Copy link
Owner

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants