Limit the size of 'actual'/'expected' strings before generating a diff #4638
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.
Description
Mocha prints its own diff on assertion errors by stringifying
err.actual
anderr.expected
, then passing both strings to jsdiff for generating a diff-patch. For big strings this synchronous process can take several minutes.jsdiff has some known performance issues, so in mid-term we evtl. should evaluate a jsdiff alternative.
On the other hand it's not a good idea to calculate a diff for two huge strings, even with a faster algorithm. We should limit the size of the input strings, as eg. done by Node's
assert
as well.Description of the Change
err.actual
anderr.expected
... Lines skipped
Applicable issues
closes #3675