Skip to content

Conversation

@mmarchini
Copy link
Contributor

Add some extra checks to make sure we won't crash when stringifying a
(possibly corrupted) SlicedString.

Add some extra checks to make sure we won't crash when stringifying a
(possibly corrupted) SlicedString.
@mmarchini
Copy link
Contributor Author

I had this issue in the wild. Couldn't come up with a test case for it though...

mmarchini added a commit that referenced this pull request Jan 21, 2020
Add some extra checks to make sure we won't crash when stringifying a
(possibly corrupted) SlicedString.

PR-URL: #332
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
@mmarchini
Copy link
Contributor Author

Landed in bff9f5e

@mmarchini mmarchini closed this Jan 21, 2020
@coveralls
Copy link

coveralls commented Dec 13, 2024

Pull Request Test Coverage Report for Build 6fa93812eafcac88c45bd0de0d399201c00e95af-PR-332

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

Details

  • 3 of 3 (100.0%) changed or added relevant lines in 1 file are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage increased (+2.3%) to 79.4%

Totals Coverage Status
Change from base Build 878b514e2919e1adf7974694bf36cdd7286cdec8: 2.3%
Covered Lines: 3625
Relevant Lines: 4556

💛 - Coveralls

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 this pull request may close these issues.

3 participants