Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork32k
gh-130655: Add a test for corrupt MO files in gettext#131911
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
This comment was marked as resolved.
This comment was marked as resolved.
sry misclick, I wanted to abandon a pending review :') |
a126cef
intopython:mainUh oh!
There was an error while loading.Please reload this page.
…honGH-131911)(cherry picked from commita126cef)Co-authored-by: Tomas R. <tomas.roun8@gmail.com>
…honGH-131911)(cherry picked from commita126cef)Co-authored-by: Tomas R. <tomas.roun8@gmail.com>
GH-132079 is a backport of this pull request to the3.13 branch. |
GH-132080 is a backport of this pull request to the3.12 branch. |
Thanks for the review@picnixz! |
Uh oh!
There was an error while loading.Please reload this page.
It is possible to have a corrupt MO file where the message offsets and lengths are larger than the size of the file being parsed. gettext detects this and raises an error, however this is currently not tested. This PR adds a test for it.
gettext
#130655