Run cli command with --samples 3 will trigger error
#60
Comments
nogamenofun98
changed the title
--samples 3 will trigger error
|
Same here using the unlighthouse command with an unlighthouse.config.ts file with scanner.samples 3 set. Reproduction System / Nuxt Info |
|
Hi, thanks for the issue :) I am not able to replicate it personally, though this may be resolved with Unlighthouse 0.7.0 with the updated Puppeteer dependency. If it still doesn't work you can try to pass the config: |
|
thanks @harlan-zw I tried again with 0.7.1, and with using chrome.useSystem: false, but this time got a different error: |
I tried to put Unlighthouse version: Here is my config: |
|
Sorry I'd like to help further but I can't replicate on my Linux laptop, if any Windows users have capacity to help me debug it would be appreicated. |
|
I saw this issue when I tried using samples 3 as well, I'll see if I can debug it and figure out what the issue is. From what I've read, it's a Lighthouse 9 issue, that's resolved in 10. I'm not sure @harlan-zw what your plans are for keeping up to date with lighthouse versions. |
|
I have made two attempts to upgrade so far, it hasn't been very successful as there's many breaking changes (cjs support is dropped). Will attempt again soon . |
|
This has also been happening to me since February. It seemed to me to happen after my chrome upgraded to version 110 +. I updated my local versions of Node, NPM, unlighthouse, but still getting the same errors. I also tried to set the downloadFallbackVersion to I get this error if my sampling rate is anything more than 1. |
|
Just ran into this issue myself. Seems related to this. |
|
Just to give more information about the problem, it also occurs for me on MacOS when sample is past 2. I don't have the time to take a look to fix it, sorry. I love the library tho. |
I'm really looking forward to this. This is especially important in CI environment since the CPU/Memory power varies in quite a lot when running against multiple pages. Without |
|
The problem can be resolved by bumping the version of the Lighthouse package inside @unlighthouse/core. #183 made that changes to the codebase. However, the current version (v0.10.6) still uses Lighthouse (^9.6.8) so we may need to wait for the new version release. For those interested, here's a GitHub workflow file where the Lighthouse version is manually updated. |
Just tried this. Though |
Describe the bug
After running a while, the cli response the following:
Error: Cannot create new tab, and no tabs already open.
at C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\connections\cri.js:45:35
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Driver.connect (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:119:5)
at async Function.run (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\gather-runner.js:484:7)
at async Function._gatherArtifactsFromBrowser (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:264:23)
at async Function.gather (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:170:21)
at async lighthouse (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\index.js:50:21)
at async file:https:///C:/Users/ant008/AppData/Local/npm-cache/_npx/9c5b11f5f0ea845b/node_modules/@unlighthouse/core/dist/process/lighthouse.mjs:16:26
Error: Cannot create new tab, and no tabs already open.
at C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\connections\cri.js:45:35
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Driver.connect (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:119:5)
at async Function.run (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\gather-runner.js:484:7)
at async Function._gatherArtifactsFromBrowser (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:264:23)
at async Function.gather (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:170:21)
at async lighthouse (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\index.js:50:21)
at async file:https:///C:/Users/ant008/AppData/Local/npm-cache/_npx/9c5b11f5f0ea845b/node_modules/@unlighthouse/core/dist/process/lighthouse.mjs:16:26
C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:348
asyncTimeout = setTimeout(reject, timeout, new LHError(LHError.errors.PROTOCOL_TIMEOUT, {
^
LighthouseError [LHError]: PROTOCOL_TIMEOUT
at C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:348:50
at new Promise ()
at Driver.sendCommandToSession (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:346:28)
at Driver.sendCommand (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:369:17)
at Object.clearDataForOrigin (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver\storage.js:58:19)
at Function.disposeDriver (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\gather-runner.js:179:39)
at Function.run (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\gather-runner.js:532:20)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Function._gatherArtifactsFromBrowser (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:264:23)
at async Function.gather (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:170:21) {
code: 'PROTOCOL_TIMEOUT',
friendlyMessage: {
i18nId: 'lighthouse-core/lib/lh-error.js | protocolTimeout',
values: {
errorCode: 'PROTOCOL_TIMEOUT',
protocolMethod: 'Storage.clearDataForOrigin'
},
formattedDefault: 'Waiting for DevTools protocol response has exceeded the allotted time. (Method: Storage.clearDataForOrigin)'
},
lhrRuntimeError: true,
protocolMethod: 'Storage.clearDataForOrigin'
}
Node.js v17.1.0
ERROR Failed to run lighthouse for route Command failed with exit code 1: node C:/Users/ant008/AppData/Local/npm-cache/_npx/9c5b11f5f0ea845b/node_modules/@unlighthouse/core/dist/process/lighthouse.mjs --cache=true --routeReport={"route":{"url":"https://next.syopex.com/brand/skll"},"artifactPath":"D:\\Frontend\\unlighthouse\\.unlighthouse\\next.syopex.com\\e6ae\\reports\\brand\\skll"} --lighthouseOptions={"onlyCategories":["performance","accessibility","best-practices","seo"],"throttlingMethod":"provided","throttling":{"rttMs":0,"throughputKbps":0,"cpuSlowdownMultiplier":1,"requestLatencyMs":0,"downloadThroughputKbps":0,"uploadThroughputKbps":0},"formFactor":"mobile","screenEmulation":{"mobile":true,"width":360,"height":640,"deviceScaleFactor":2}} --port=54889
Error: Cannot create new tab, and no tabs already open.
at C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\connections\cri.js:45:35
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at async Driver.connect (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:119:5)
at async Function.run (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\gather-runner.js:484:7)
at async Function._gatherArtifactsFromBrowser (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:264:23)
at async Function.gather (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\runner.js:170:21)
at async lighthouse (C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\index.js:50:21)
at async file:https:///C:/Users/ant008/AppData/Local/npm-cache/_npx/9c5b11f5f0ea845b/node_modules/@unlighthouse/core/dist/process/lighthouse.mjs:16:26
C:\Users\ant008\AppData\Local\npm-cache_npx\9c5b11f5f0ea845b\node_modules\lighthouse\lighthouse-core\gather\driver.js:348
asyncTimeout = setTimeout(reject, timeout, new LHError(LHError.errors.PROTOCOL_TIMEOUT, {
Reproduction
npx unlighthouse-puppeteer --site next.syopex.com --samples 3 OR npx unlighthouse --site next.syopex.com --samples 3
System / Nuxt Info
System: OS: Windows 10 10.0.19045 CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz Memory: 7.24 GB / 15.92 GB Binaries: Node: 17.1.0 - C:\Program Files\nodejs\node.EXE npm: 8.1.2 - C:\Program Files\nodejs\npm.CMD Browsers: Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.35) Internet Explorer: 11.0.19041.1566The text was updated successfully, but these errors were encountered: