WICG / crash-reporting

Crash reporting (from Web Perf WG)
https://wicg.github.io/crash-reporting/
Other
8 stars 7 forks source link

Add optional call stacks for unresponsive reports #16

Closed clelland closed 3 months ago

clelland commented 3 months ago

This isn't super rigorous yet; I'm writing up a better processing model which should allow this to define exactly when and how a call stack is collected and added to the report. It should include some samples, too.


:boom: Error: 500 Internal Server Error :boom:

PR Preview failed to build. (Last tried on Jul 17, 2024, 3:48 PM UTC).

More PR Preview relies on a number of web services to run. There seems to be an issue with the following one: :rotating_light: [Spec Generator](https://www.w3.org/2015/labs/) - Spec Generator is the web service used to build specs that rely on ReSpec. :link: [Related URL]([object Object]) ``` 🕵️‍♀️ That doesn't seem to be a ReSpec document. Please check manually: http://localhost:8082/uploads/Tdd5QD/index.html?force=1&isPreview=true%3Fforce%3D1&isPreview=true&publishDate=2024-07-17 ``` _If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please [file an issue](https://github.com/tobie/pr-preview/issues/new?title=Error%20not%20surfaced%20properly&body=See%20WICG/crash-reporting%2316.)._
clelland commented 3 months ago

@issackjohn, @sethbrenith FYI - this is a start of a spec for the work on #12

issackjohn commented 3 months ago

@clelland Looks like I missed this. LGTM.