Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add ability to tune / remove default puppeteer timeout
See original GitHub issue🧩 Feature request
Description
Sometimes I need to wait for a very long time until page gets ready to process it. So I add manualIdle check, but after 25sec puppeteer processes the page, even if there were no signal that page is ready.
Describe the solution you’d like
Some configuration parameter which will allow to tune this timeout or disable it at all.
Also it would be great to add parameter which make puppeteer plugin throw an error and stops processing in case such timeout is reached instead of silently continue process.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@lamp-of-god I just now noticed your response. That is a compelling use case. We will have another discussion about this. This will probably swing the discussion. I’ll let you know in a little while.
As I saw recently, nothing has changed. Had to update my Scully configs and ended up hot patching the puppeteer plugin. Made a Gist for this: https://gist.github.com/jsanta/4adbcdb00409c81853c8b9241fe36ccc