resourceChangedPriority and request.priorty errors
See original GitHub issueUsing Chrome Canary Version 55.0.2844.0 canary (64-bit) on OS X, launched via
$ npm explore -g lighthouse -- npm run chrome
I consistently get this error when running a full audit suite:
$ node lighthouse-cli/index.js https://ifixit-pwa.appspot.com
... logged output ...
/Users/jeffy/git/lighthouse/lighthouse-core/lib/network-recorder.js:90
this.networkManager._dispatcher.resourceChangedPriority(data.requestId,
^
TypeError: this.networkManager._dispatcher.resourceChangedPriority is not a function
at NetworkRecorder.onResourceChangedPriority (/Users/jeffy/git/lighthouse/lighthouse-core/lib/network-recorder.js:90:37)
at emitOne (events.js:90:13)
at Chrome.emit (events.js:182:7)
at WebSocket.<anonymous> (/Users/jeffy/git/lighthouse/lighthouse-core/node_modules/chrome-remote-interface/lib/chrome.js:360:18)
at emitTwo (events.js:100:13)
at WebSocket.emit (events.js:185:7)
at Receiver.ontext (/Users/jeffy/git/lighthouse/lighthouse-core/node_modules/ws/lib/WebSocket.js:841:10)
at /Users/jeffy/git/lighthouse/lighthouse-core/node_modules/ws/lib/Receiver.js:536:18
at /Users/jeffy/git/lighthouse/lighthouse-core/node_modules/ws/lib/Receiver.js:368:7
at /Users/jeffy/git/lighthouse/lighthouse-core/node_modules/ws/lib/PerMessageDeflate.js:249:5
When testing against a different site, I can reliably get a different error:
$ node lighthouse-cli/index.js https://airhorner.com
... logged output ...
Runtime error encountered: [TypeError: request.priority is not a function]
TypeError: request.priority is not a function
at CriticalRequestChains.isCritical (/Users/jeffy/git/lighthouse/lighthouse-core/gather/computed/critical-request-chains.js:50:61)
at /Users/jeffy/git/lighthouse/lighthouse-core/gather/computed/critical-request-chains.js:62:64
at Array.filter (native)
at CriticalRequestChains.getChains (/Users/jeffy/git/lighthouse/lighthouse-core/gather/computed/critical-request-chains.js:62:45)
at CriticalRequestChains.request (/Users/jeffy/git/lighthouse/lighthouse-core/gather/computed/critical-request-chains.js:143:17)
at Object.computedArtifacts.(anonymous function) [as requestCriticalRequestChains] (/Users/jeffy/git/lighthouse/lighthouse-core/gather/gather-runner.js:352:41)
at Function.audit (/Users/jeffy/git/lighthouse/lighthouse-core/audits/critical-request-chains.js:44:22)
at /Users/jeffy/git/lighthouse/lighthouse-core/runner.js:97:24
Issue Analytics
- State:
- Created 7 years ago
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Cannot Modify Rule and Priority Simultaneously #293 - GitHub
Terraform / Azure will error out saying that you cannot have duplicate priorities. Rerun terraform apply and watch it make the correct changes....
Read more >Boost Resource Loading With fetchpriority, A New Priority Hint
This new attribute will enable us to fine-tune relative resource priority, improve LCP performance, deprioritize JavaScript fetch calls, ...
Read more >Restrict Changing of Priority - ServiceNow Community
I am trying to restrict the lowering of a priority. ... Error: Priority error.PNG. We do NOT use impact and Urgency.
Read more >Impact, Urgency & Priority: Understanding the Matrix
Priority is the intersection of impact and urgency. Considering impact and urgency offers your company a clearer understanding of what is more ...
Read more >Terraform ALB error "Error creating LB Listener Rule: Priority X ...
So the solution is to either have new priority number in new resource, or leave resource name the same every time (rule1) in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thanks! Mystery solved, and it works as expected now. 👍
Let me know if the problem is still there after you do that.