Lighthouse could not test page - LHError: PROTOCOL_TIMEOUT
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- javascript
- Domain
- performance, tooling
Research direction
Start with index.js lines 36-68, then compare the documented --lighthouse.config and --lighthouse.flags options with the Chrome flags configured there. Reproduce the PROTOCOL_TIMEOUT against the localhost page and determine whether an additional flag can be passed; done means the supported configuration path is documented or the issue is narrowed to an upstream Lighthouse failure.
Written by the indexing model from the issue text.
Description
Your question
Hi
I'm trying to test pages with sitespeedio/sitespeed.io:25.11.0-plus1
But receiving the error:
ERROR: Lighthouse could not test http://localhost:3000/testPage please create an upstream issue: https://github.com/GoogleChrome/lighthouse/issues/new?assignees=&labels=bug&template=bug-report.yml LHError: PROTOCOL_TIMEOUT
at /lighthouse/node_modules/lighthouse/lighthouse-core/gather/driver.js:348:50.....
After researching, one possible solution that could help is to add a chrome flag "--disable-dev-shm-usage" (https://github.com/GoogleChrome/lighthouse/issues/6512)
But none of the options for passing flags to the lighthouse plugin, as I see it, does not work for me (from --lighthouse.config config.js or --lighthouse.flags flag.json)
And as I see here https://github.com/sitespeedio/plugin-lighthouse/blob/main/index.js#L36-L68 the chrome flags are already set but without the ability to pass additional flags into it (maybe I'm wrong).
@soulgalore could you please tell me if there are any other ways to pass chrome flags to the lighthouse plugin?
Or maybe there are other ways to fix the error?
- Dominant language
- JavaScript
- Stars
- 31
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from sitespeedio/plugin-lighthouse
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
sitespeedio/plugin-lighthouse#136 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#134 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#133 · 1 comment ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
sitespeedio/plugin-lighthouse#126 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
sitespeedio/plugin-lighthouse#120 · 7 comments ·
All issues in sitespeedio/plugin-lighthouse
Similar issues
-
bot:ai-assisted component:compact-js status:untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
midnightntwrk/midnight-sdk#403 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
DavidAnson/markdownlint-cli2#940 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
githubnext/gh-aw-workshop#3692 ·
-
agent/guide documentation hive/hosted-available-lke648397-260827-5n31
Difficulty 2/5 1-3 hours Newbie friendliness 90/100