GoogleChrome / GoogleChrome/lighthouse
Add Tracing failed to knownBugPatterns with a "use official build message"
- Dominant language
- JavaScript
- Stars
- 30.8k
- Forks
- 9.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 20
Description
#### Provide the steps to reproduce
1. Run LH on https://reg-game.netlify.com/
#### What is the current behavior?
The following message appears
> Ah, sorry, we ran into an error.
```
Protocol error (Tracing.end): Tracing failed
Channel: DevTools
Initial URL: https://reg-game.netlify.com/
Chrome Version: 78.0.3882.0
Stack Trace: Error: Protocol error (Tracing.end): Tracing failed
at Function.fromProtocolMessage (devtools://devtools/remote/serve_file/@19d4547535ab5aba70b4730443f84e8153052174/audits_worker/audits_worker_module.js:1603:121)
at eval (devtools://devtools/remote/serve_file/@19d4547535ab5aba70b4730443f84e8153052174/audits_worker/audits_worker_module.js:1209:253)
```

#### What is the expected behavior?
No error appears
#### Environment Information
* Affected Channels: DevTools
* Lighthouse version:
* Chrome version: Chromium Version 78.0.3882.0 (Developer Build) (64-bit)
* Operating System: MacOS 10.15.2 (19C57)
Contributor guide
Research direction
Locate the knownBugPatterns entry point in the Lighthouse repository and review the issue discussion for the intended wording. Add the Tracing failed pattern with a message directing users to an official build, then verify the existing known-bug matching tests if they cover this list.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- devtools, javascript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100