Skip to content

Add test case as example of Git commit with invalid data #456

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

Merged
merged 2 commits into from
May 30, 2016

Conversation

nvie
Copy link
Contributor

@nvie nvie commented May 30, 2016

This is a real commit from the microjs.com open source project, see microjs/microjs.com@7e8457c, which is declared to be encoded in UTF-8, but contains invalid bytes.

This makes GitPython choke on it while decoding. Rather than choking, this should instead accept the error and replace the invalid bytes by the � (\x80) char.

This is a real commit from the microjs.com open source project, see
microjs/microjs.com@7e8457c,
which is declared to be encoded in UTF-8, but contains invalid bytes.

This makes GitPython choke on it while decoding.  Rather than choking,
this should instead accept the error and replace the invalid bytes by
the �  (\x80) char.
@nvie nvie force-pushed the fix-for-invalid-data-in-commits branch from f0ef7af to db9a8d5 Compare May 30, 2016 14:32
Previously, GitPython chokes on this while decoding.  Rather than
choking, instead accept the error and replace the invalid bytes by the
� (\x80) char.
@nvie nvie force-pushed the fix-for-invalid-data-in-commits branch from db9a8d5 to 79c99c0 Compare May 30, 2016 14:37
@Byron Byron added this to the v2.0.4 - Bugfixes milestone May 30, 2016
@Byron Byron merged commit 79fdaf3 into master May 30, 2016
@Byron
Copy link
Member

Byron commented May 30, 2016

Good catch ! Thanks for the PR !

@nvie nvie deleted the fix-for-invalid-data-in-commits branch May 30, 2016 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants