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

Errors after parsing are getting eaten by library #54

Closed
IanShoe opened this issue Feb 17, 2016 · 1 comment
Closed

Errors after parsing are getting eaten by library #54

IanShoe opened this issue Feb 17, 2016 · 1 comment

Comments

@IanShoe
Copy link

IanShoe commented Feb 17, 2016

I have run into a case where I complete a successful pdf parsing, but have an error down the road in my app that gets caught within the parser library. The problem is that the library actually ends up catching the error on line87 and eating it. I am given no indicators as to what happened or the ability to handle it properly in my app.

Here's a script that will demonstrate parsing a pdf, and then intentionally throwing an error.
https://gist.github.com/IanShoe/e92ee20f4862b187f9ae

modesty pushed a commit that referenced this issue Mar 10, 2016
@modesty
Copy link
Owner

modesty commented Mar 10, 2016

fixed in v1.1.1.

@modesty modesty closed this as completed Mar 10, 2016
modesty added a commit that referenced this issue Nov 10, 2023
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

No branches or pull requests

2 participants