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

Navigation Timeout Exceeded #131

Closed
lewisdonovan opened this issue Jan 29, 2018 · 12 comments
Closed

Navigation Timeout Exceeded #131

lewisdonovan opened this issue Jan 29, 2018 · 12 comments
Labels

Comments

@lewisdonovan
Copy link

lewisdonovan commented Jan 29, 2018

I'm getting Error: Navigation Timeout Exceeded: 30000ms exceeded when running react-snap locally. It renders all the top-level pages as expected, and then when it hits the first detail-view URL it throws the error.

It wasn't doing this before and I haven't changed any code in the component, although the page itself is new, as new items have been added to the CMS and are now being pulled from the API. I have tried removing the offending item and running build again, but the same error happens when it gets to the first detail-view URL again (even though it's a different item).

Error log pasted below:

info it worked if it ends with ok
verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'run', 'build' ]
info using npm@5.6.0
info using node@v8.9.3
verbose run-script [ 'prebuild', 'build', 'postbuild' ]
info lifecycle magician-prod@0.1.0~prebuild: magician-prod@0.1.0
info lifecycle magician-prod@0.1.0~build: magician-prod@0.1.0
verbose lifecycle magician-prod@0.1.0~build: unsafe-perm in lifecycle true
verbose lifecycle magician-prod@0.1.0~build: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/dono023/Desktop/react-projects/magician-prod/node_modules/.bin:/Users/dono023/torch/install/bin:/Applications/anaconda2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/go/bin:/Users/you/torch/install/bin
verbose lifecycle magician-prod@0.1.0~build: CWD: /Users/dono023/Desktop/react-projects/magician-prod
silly lifecycle magician-prod@0.1.0~build: Args: [ '-c', 'react-scripts build' ]
silly lifecycle magician-prod@0.1.0~build: Returned: code: 0  signal: null
info lifecycle magician-prod@0.1.0~postbuild: magician-prod@0.1.0
verbose lifecycle magician-prod@0.1.0~postbuild: unsafe-perm in lifecycle true
verbose lifecycle magician-prod@0.1.0~postbuild: PATH: /usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/Users/dono023/Desktop/react-projects/magician-prod/node_modules/.bin:/Users/dono023/torch/install/bin:/Applications/anaconda2/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/opt/X11/bin:/usr/local/go/bin:/Users/you/torch/install/bin
verbose lifecycle magician-prod@0.1.0~postbuild: CWD: /Users/dono023/Desktop/react-projects/magician-prod
silly lifecycle magician-prod@0.1.0~postbuild: Args: [ '-c', 'react-snap' ]
silly lifecycle magician-prod@0.1.0~postbuild: Returned: code: 1  signal: null
info lifecycle magician-prod@0.1.0~postbuild: Failed to exec postbuild script
verbose stack Error: magician-prod@0.1.0 postbuild: `react-snap`
verbose stack Exit status 1
verbose stack     at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:285:16)
verbose stack     at emitTwo (events.js:126:13)
verbose stack     at EventEmitter.emit (events.js:214:7)
verbose stack     at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
verbose stack     at emitTwo (events.js:126:13)
verbose stack     at ChildProcess.emit (events.js:214:7)
verbose stack     at maybeClose (internal/child_process.js:925:16)
verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:209:5)
verbose pkgid magician-prod@0.1.0
verbose cwd /Users/dono023/Desktop/react-projects/magician-prod
verbose Darwin 16.7.0
verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
verbose node v8.9.3
verbose npm  v5.6.0
error code ELIFECYCLE
@stereobooster
Copy link
Owner

Can be related puppeteer/puppeteer#1908, peterbe/minimalcss#112

@stereobooster
Copy link
Owner

What version of react-snap do you use? If it is 1.11 can you try 1.10?

@lewisdonovan
Copy link
Author

Rolling back to 1.10.0 seems to be solving this

@stereobooster
Copy link
Owner

stereobooster commented Jan 29, 2018

In 1.11.0 I updated to the latest Puppeteer 1.0. I suspect they broke something

@ghost
Copy link

ghost commented Feb 5, 2018

Having the same issue here, but with no effect when rolled back to 1.10.0. Any ideas?

@stereobooster
Copy link
Owner

stereobooster commented Feb 5, 2018

@gopchi do you have some third-party resources? Can you try to create reproducible example? DId you tried rm -rf node_modules && yarn install?

@ghost
Copy link

ghost commented Feb 12, 2018

@stereobooster doing what you said worked, but now in the postbuild process there is an error saying Unhandled Promise rejection... for some routes. Despite that it builds the routes and they work.

@stereobooster
Copy link
Owner

@gopchi can you copy/paste error message. It can happen that those notifications are from your application, not from react-snap

@ghost
Copy link

ghost commented Feb 14, 2018

@stereobooster There it is:

ERROR: The process with PID 13328 (child process of PID 12024) could not be terminated. Reason: The operation attempted is not supported. (node:20400) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 2): Error: Command failed: taskkill /pid 12024 /T /F

(node:20400) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It happens on different route every time I try to build. Sometimes they are all ok except the last one. Other times 4 of the routes get this error.

Using node v8.9.4

@stereobooster
Copy link
Owner

@gopchi this sounds like an issue in puppeteer and not the same as described in this ticket. You can try create reproducible demo and open ticket here or in puppeteer issue tracker. If you open ticket here I will try to investigate and eventually will open ticket in puppeteer issue tracker.

@ghost
Copy link

ghost commented Feb 14, 2018

@stereobooster Okay, thanks I will open a new issue on this error.

@stereobooster
Copy link
Owner

Closed in favour of #240

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants