Increase Maven maxBuffer to 50MB and add buffer overflow error handling #11
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.
Purpose: Maven dependency extraction fails when processing large projects with extensive dependency trees, as the default Node.js buffer size (1MB) is insufficient for capturing verbose Maven output during dependency downloads and analysis. This causes silent failures or truncated output that prevents accurate dependency evaluation.
Approach:
isMaxBufferError()detection function to identify buffer overflow errors similar to existingisTimeoutError()patternlicense:add-third-partyanddependency:list)