-
-
Notifications
You must be signed in to change notification settings - Fork 141
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 timeout error for requests blocked by phantomjs #217
Conversation
if (entry.isBlocked) { | ||
return; | ||
} else { | ||
phantomas.emit('abort', entry, res); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's worth logging this failed request details for debugging purposes as this can indicate problems on PhantomJS side or on the server.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Agreed.
Shall I investigate a bit more or do you want do it yourself?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@stefanjudis: please add logging of request URL.
I assume that this issue can be reproduced by:
phantomas --url http://www.nicola-zanon.com/
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Interesting, just tested on the URL above. Works fine, no timeouts (using PhantomJS v1.9.2 / the latest phantomas dev version). Can you post stderr when running in --verbose
mode on Gist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://gist.github.com/stefanjudis/22fb165a75d6db5ba94c
It never succeeds.
👍 |
Fix timeout error for requests blocked by phantomjs
This fix does not work well with base64 encoded data:
Will fix it as a part of #216 |
👍 |
For this page I noticed the behaviour of constant failing of phantomas.
The reason was, that phantomjs blocks one request and phantomas never counts this request as done.
Result is constant timeout failing.
Referenced issue: stefanjudis/grunt-phantomas#21