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

Throw error explicitly using the callback instead of failing due to "Cannot read property 'filename' of undefined" #643

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

omrilit
Copy link

@omrilit omrilit commented Aug 18, 2021

No description provided.

…ng due to "Cannot read property 'filename' of undefined" (#1)
@jagadeesh93
Copy link

@omrilit Hii , I am also facing the same issue on the version 3.0.1, Is there any fix for this , Thanks in advance

@omrilit
Copy link
Author

omrilit commented Nov 29, 2021

@omrilit Hii , I am also facing the same issue on the version 3.0.1, Is there any fix for this , Thanks in advance

@jagadeesh93 not that I am aware of. I've just forked the repo and added this PR's content. You can see it at https://github.com/salto-io/node-html-pdf

Copy link

@barakplasma barakplasma left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one line change looks good to me. We've also been experiencing this issue on a regular basis since upgrading to v3.0.1

@barakplasma
Copy link

barakplasma commented Feb 8, 2022

I have a suspicion that this bug might be caused by phantomjs failing but html-pdf not catching it and counting on there being a file when there isn't one. PR 644 might solve this issue

@barakplasma
Copy link

For a patch in the meanwhile, see #644 (comment) . I'm going to rollout the patch in prod, ping me later if you're interested in whether it solved the issue for me.

@omrilit
Copy link
Author

omrilit commented Feb 8, 2022

@barakplasma it would be great if you could write here if it worked for you.

@barakplasma
Copy link

I haven't deployed to prod yet, so no news.
However, I did write a case to recreate this particular bug in my branch which shows that the fix in #644 does prevent the bug we are experiencing in this issue.

@barakplasma
Copy link

@omrilit your mileage may vary, but I deployed the fix in #644 to prod, and we haven't had that error since

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.

None yet

4 participants