You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Unhandled Rejection at: Promise Promise {
<rejected> Error: Invalid response status code: 404
at ./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:119:18
at Fetcher._onRequestPaused (./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:75:13)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at Driver._handleProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/driver.js:299:24)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at CalibreProtocol.emitProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:148:24)
at CalibreProtocol.handleRawMessage (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:113:12)
at WebSocket.<anonymous> (./node_modules/lighthouse/lighthouse-core/gather/connections/cri.js:72:37)
} reason: Error: Invalid response status code: 404
at ./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:119:18
at Fetcher._onRequestPaused (./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:75:13)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at Driver._handleProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/driver.js:299:24)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at CalibreProtocol.emitProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:148:24)
at CalibreProtocol.handleRawMessage (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:113:12)
at WebSocket.<anonymous> (./node_modules/lighthouse/lighthouse-core/gather/connections/cri.js:72:37)
(node:25717) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 10)
Error: Invalid response status code: 404
at ./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:119:18
at Fetcher._onRequestPaused (./node_modules/lighthouse/lighthouse-core/gather/fetcher.js:75:13)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at Driver._handleProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/driver.js:299:24)
at EventEmitter.emit (events.js:315:20)
at EventEmitter.emit (domain.js:482:12)
at CalibreProtocol.emitProtocolEvent (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:148:24)
at CalibreProtocol.handleRawMessage (./node_modules/lighthouse/lighthouse-core/gather/connections/connection.js:113:12)
at WebSocket.<anonymous> (./node_modules/lighthouse/lighthouse-core/gather/connections/cri.js:72:37)
I'm seeing the error in Node and when using the Lighthouse CLI.
Thanks for filing @mikedijkstra! The sendCommand ones are an easy fix but I'm not immediately seeing how the invalid status code ones are unhandled 🤔 we'll have to investigate.
My preliminary investigation results:
The only place we use the fetcher is in source maps where it is await'd properly, so it must be internal to fetcher.
I was guessing that requestInterceptionPromise was rejecting after our timeout rejected and that somehow leads to the unhandled rejection.
This doesn't hold up with my understanding of Promise.race though, and toy example won't repro either... not sure how it's happening
constrejectIn1s=newPromise((r,reject)=>setTimeout(()=>reject('foo'),1000))// this doesn't lead to an unhandled promise rejectionconstresolvein500ms=newPromise(r=>setTimeout(r,500))Promise.race([rejectIn1s,resolvein500ms]).then(()=>console.log('done')).finally(()=>console.log('finally'))
We're seeing a number of errors being thrown from
lighthouse-core/gather/fetcher.js
as unhandled promise rejections.Examples of errors:
Error output
I'm seeing the error in Node and when using the Lighthouse CLI.
Provide the steps to reproduce
Run:
What is the current behavior?
Lighthouse returns
Unhandled Rejection. Reason: Error: Invalid response status code: 404
. See full output.What is the expected behavior?
Lighthouse report is generated and opened in the browser
Environment Information
The text was updated successfully, but these errors were encountered: