-
Notifications
You must be signed in to change notification settings - Fork 373
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add crash retriever script #2168
Conversation
b0ad626
to
c21744b
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So nice!
# }, | ||
# "event": "crash-panic", | ||
# "timestamp": "2023-05-11T20:17:52.479000+00:00", | ||
# "person": null, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is person
null
? It would be so nice to be able to say "this crash affects 3 distinct users`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is
person
null
?
This is a bit of a weird field that can be safely ignored; the distinct_id
just above gives us all the information we need.
It would be so nice to be able to say "this crash affects 3 distinct users`
That's exactly what this PR does! I need to modify the headers' template to reflect that
* add crash fetcher script * newline * fmt * typo * uniques * fmt * format again........ * woops -- missing signals * shebang, and chmod +x * better header template --------- Co-authored-by: Emil Ernerfeldt <[email protected]>
* add crash fetcher script * newline * fmt * typo * uniques * fmt * format again........ * woops -- missing signals * shebang, and chmod +x * better header template --------- Co-authored-by: Emil Ernerfeldt <[email protected]>
Fetch user crashes from PostHog database, deduplicates them, and prefill issue reports for them.
Usage:
Optionally, you can filter out data older than a given timestamp:
See also:
Live demo
2 distinct user(s) affected by panic crash @
winit-0.28.1/src/platform_impl/linux/mod.rs:757
2023-05-15T21:20:44.358000+00:00
2023-05-19T15:42:51.622000+00:00
['1.67.1 (d5a82bbd2 2023-02-07)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by panic crash @
wgpu-0.15.1/src/backend/direct.rs:316
2023-05-15T14:43:58.362000+00:00
2023-05-20T13:22:17.682000+00:00
['1.67.1 (d5a82bbd2 2023-02-07)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by panic crash @
winit-0.28.1/src/platform_impl/linux/wayland/window/mod.rs:327
2023-05-19T09:39:05.464000+00:00
2023-05-20T05:50:40.112000+00:00
['1.67.1 (d5a82bbd2 2023-02-07)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by panic crash @
arrow2-0.16.0/src/array/growable/binary.rs:73
2023-05-20T05:19:00.353000+00:00
2023-05-20T05:19:00.353000+00:00
['1.67.1 (d5a82bbd2 2023-02-07)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by panic crash @
wgpu-0.15.1/src/backend/direct.rs:316
2023-05-18T23:35:28.850000+00:00
2023-05-20T02:27:01.859000+00:00
['1.68.2 (9eb3afe9e 2023-03-27)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by panic crash @
winit-0.28.6/src/platform_impl/linux/mod.rs:757
2023-05-15T12:50:30.691000+00:00
2023-05-15T12:50:30.691000+00:00
['1.68.2 (9eb3afe9e 2023-03-27)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by signal crash @
SIGABRT
2023-05-15T13:46:46.504000+00:00
2023-05-15T13:46:46.504000+00:00
['1.68.2 (9eb3afe9e 2023-03-27)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
1 distinct user(s) affected by signal crash @
SIGABRT
2023-05-14T16:47:35.588000+00:00
2023-05-14T16:47:35.588000+00:00
['1.67.1 (d5a82bbd2 2023-02-07)']
['0.5.1']
['x86_64-unknown-linux-gnu']
Backtrace:
PR Build Summary: https://build.rerun.io/pr/2168