Skip to content
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

fix: issue #373: handle bad encoding expcetion by start page renderin… #378

Merged
merged 1 commit into from
Dec 28, 2024

Conversation

modesty
Copy link
Owner

@modesty modesty commented Dec 28, 2024

…g after page operator list is resolved, add i373_err_broken.pdf to verify

to verify:

  1. npm run test and npm run test:forms should all pass
  2. npm run test:misc should see list of success and error and total counter matches expected
  3. npm run test:e will parse i373_err_broken.pdf only, exception should be handled gracefully

…g after page operator list is resolved, add i373_err_broken.pdf to verify
@modesty modesty merged commit 7721899 into master Dec 28, 2024
1 check passed
@modesty modesty deleted the scratch/handleBadEncodingException branch December 28, 2024 05:00
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.

1 participant