Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
When we fail processing a published profile because its version is too high, we should check if the service worker has updated
See original GitHub issueRegularly, when we increase the processed profile version, then it could happen that a user will get an error when trying to display a shared profile with this newer version, while he still has an outdated version of perf-html cached locally by the service worker.
If we have an error while processing the downloaded profile, we can check if we have a new service worker waiting, using something like:
navigator.serviceWorker.ready.then(registration => // check registration.waiting)
Or dispatch an action for onUpdated in https://github.com/devtools-html/perf.html/blob/f9d3c2e425d5124d1a9e4844cd662eff0ab3ebe0/src/index.js#L14-L18 so that we know a new SW is ready to be used.
Issue Analytics
- State:
- Created 6 years ago
- Comments:5 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’d like to take a shot at it quickly.
Just ran into this again. Automatic refresh would be amazing and probably solves 99% of the issues caused by outdated SWs!