Navigation Timeout Exceeded with waitUntil: networkidle* #230
Comments
This doesn't solve issue in general it simply masks the problem, though it can work in your case. Issue with timeout is known #131. It was reported in puppeteer, but it still reported by users from time to time |
|
@stereobooster, thanks for the quick reply! I noticed #131 but since the advice over there is to use I'll try downgrading to In the end the |
|
You can use this one https://github.com/peterbe/minimalcss/pull/199/files |
|
@stereobooster, I've done some more testing using the tracker you've linked to in the previous comment. I've modified it a little bit to make it easier to debug my case: const createTracker = page => {
const requests = new Set();
const onStarted = request => {
console.log('started', request._url);
return requests.add(request);
};
const onFinished = request => {
console.log('finished', request._url);
return requests.delete(request);
};
const onFailed = request => {
console.log('FAILED', request._url);
return requests.delete(request);
};
page.on('request', onStarted);
page.on('requestfinished', onFinished);
page.on('requestfailed', onFailed);
return {
urls: () => Array.from(requests).map(r => r.url()),
dispose: () => {
console.log('requests', requests);
page.removeListener('request', onStarted);
page.removeListener('requestfinished', onFinished);
page.removeListener('requestfailed', onFailed);
}
};
};Which outputs the following: every request starts and finishes (in about 3s) and not a single one fails and I'm still running into the 30s timeout (the last 27s it just hangs). You have been evading my question about an option for the |
|
Oh, and @stereobooster, FYI: locking The question about the |
Can you also say which version of puppeteer do you use (based on |
|
|
This is the thing, in puppeteer v1.0 something is broken. Issue was reported, but closed. We need to reopen the issue and provide reproducible example |
|
Do you have any issue numbers? I might be able to build a simple docker image showing the problem if the developers over at puppeteer are interested. |
|
This is the issue puppeteer/puppeteer#1908 (comment) |
|
I have another idea, if we will add tracker (to check that all requests are finished) we can omit false positive Timeout Errors, downside of this approach is that prerendering will take longer time. |
|
Closed in favour of #240
The problem here, this will mask issue but not solve it. By adding |
I've been pulling my hair out on this for a couple of hours now and I'm hoping someone here knows what the problem might be in this case.
I'm running into the following error when executing
react-snapon our Jenkins environment, which runs Debian 8 (it runs correctly on my local macOS High Sierra machine)...I've tried playing with pretty much every setting available in
react-snapbut I couldn't get it to work so I started debugging. Turns out changingwaitUntilon this line to eitherloadordomcontentloadedresolves my issue.The strangest thing is that
networkidle*should work correctly in my mind: I've enabled logging for Puppeteer by passingDEBUG=puppeteer:sessionto the command that startsreact-snap(output is available right here: log.txt) and it just hangs for about 20 - 25 seconds when the entire output is printed which should mean there is no network traffic going on, right?My question is; would it be possible to add an option for the
waitUntilvariable toreact-snapor doesn't that work/output the correct HTML?The text was updated successfully, but these errors were encountered: