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

Timeout in Tests / Complete,Done,Error callback never called OSX #15

Closed
JBenedettini opened this issue Dec 29, 2015 · 4 comments
Closed

Comments

@JBenedettini
Copy link

This package is perfect for what i am trying to do, however i cant seem to get it work on OSX. I dont get any errors when running in my Node application, however it never fires any of its callbacks after the process function. When running the NPM Test from within the node modules, dependencies come back fine, but i get 7 errors after all having to do with Timeout after. Ive upped the Timeouts in the test and still not running. Only diffrence i have is Tesseract being version 3.04.00, however im not even trying to use OCR so i cant image this would be causing the issues.

Any help is appreciated!

@nisaacson
Copy link
Owner

Can you post some example code that is not working for you? Alternatively if you don't need the OCR support you can look at https://github.com/nisaacson/pdf-text-extract

@JBenedettini
Copy link
Author

Okay, strange enough following the exact same install practices and in the same express generated app, it works fine on my Ubuntu Dev machine. However on OSX ElCapitan i have the errors above. Not sure what it is causing the errors, il just continue to develop on the Ubuntu machine, probably better in the long run anyways!

@JBenedettini
Copy link
Author

It seems its an issue with pdftk & El Capitan, and not pdf-extract, Issue here - http://stackoverflow.com/questions/32505951/pdftk-server-on-os-x-10-11

THE FIX WAS Installing the latest MacPorts on the development machine

@huevoncito
Copy link

Running into a similar issue with OSX Sierra. Updated to latest Mac Ports but that hasn't fixed the issue. Would appreciate any ideas.

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

3 participants