[call for status]: April 2021 status update!
3 views
Skip to first unread message
William Kahn-Greene
Apr 1, 2021, 3:43:28 PM4/1/21
to crash-reporting-wg
Hi!
If you work on crash reporting related things or a crash reporting related project, please reply to this email before Tuesday, April 6th if you have status updates. Short with outlines is fine. Long is fine. If you already have some kind of status newsletter, feel free to reply with a link to that. I'll take all these replies and compile a newsletter update thing.
I want to do something like this every month. This is the first month, so we'll learn something about this time around and maybe change it next time around.
/will
Questions:
What's your team/project?
What did you accomplish? (Descriptions, bug numbers, etc)
What are you working on now or think you'll have done this month? (Descriptions, bug numbers, etc)
What do you need help with?
What are you concerned about?
What else do you think is helpful for everyone to know?
William Kahn-Greene
Apr 2, 2021, 9:44:51 AM4/2/21
to crash-reporting-wg
Picking beginning of March as the beginning of the time frame....
- What's your team/project?
- Crash ingestion pipeline: Socorro and Tecken.
- What did you accomplish? (Descriptions, bug numbers, etc)
- Improved the preview in Slack/Matrix for crash report view urls and signature report view urls.
- If there's more I can do with this to make these url previews more helpful in conversations, let me know.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1688203
- End collection of Email data in crash reports.
- I changed the collector to delete Email data for all incoming crash reports. I fixed the Firefox main and content crash reporter client code. I still have some changes to make in the webapp, but I'm waiting until May 2021 to do that.
- Many thanks to Emily, Nneka, Gabriele, Mike, and Chris for their help with this!
- https://bugzilla.mozilla.org/show_bug.cgi?id=1688883
- End collection of crash reports for Fennec
- When working on ending collection of Email data, it came up that we don't need Fennec crash reports anymore. Thus Socorro now rejects all incoming crash reports for Fennec.
- Many thanks to Emily, Stefan, Vesta, and Agi!
- https://bugzilla.mozilla.org/show_bug.cgi?id=1699239
- Fixed the webapp to automatically update the PCI device db once a week.
- Redid the "Raw data and minidumps tab in the crash report view of the webapp.
- The Crash Stats ui is confusing and clunky and I've been trying to fix bits of it over time. In this pass, I improved the tab that holds links to raw and processed crash data, minidumps, and the output of minidump-stackwalk. It should be clearer now as to what's protected data and what isn't. The links are at the top of the tab where they're easier to access. The minidump-stackwalk output is much easier to manipulate and use.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1696910
- New symbolication API microservices
- The symbolication API that Tecken has is hard to improve and there are a bunch of things we want to do with it. Because of that, I embarked on splitting it out into a separate microservice and rewriting it from the ground up using the Symbolic library. That's taken a while for a variety of reasons, but we've now got a working symbolication API in our staging environment that I think is usable.
- API url: https://symbolication.stage.mozaws.net/symbolicate/v5
- I need to write docs for it, but it uses the same payload as the existing symbolication API as documented here:
- https://tecken.readthedocs.io/en/latest/symbolication.html#symbolication-symbolicate-v5
- If you do any symbolication work, I'd love to know how it works for you and whether you encounter any issues.
- https://bugzilla.mozilla.org/show_bug.cgi?id=1636210
- What are you working on now or think you'll have done this month? (Descriptions, bug numbers, etc)
- Finishing up the new symbolication API microservice: https://bugzilla.mozilla.org/show_bug.cgi?id=1636210
- Crash Stats fixes
- (Back burner): Better Java crash report signature generation: https://bugzilla.mozilla.org/show_bug.cgi?id=1541120
- What do you need help with?
- Testing the new symbolication API. If you do anything with symbolication, please let me know.
Gabriele Svelto
Apr 2, 2021, 10:44:23 AM4/2/21
to William Kahn-Greene, crash-rep...@mozilla.com
Wow, it's a lot of work. I was wondering... once we put everything in
(from me, Kris, Alexis and Calixte) we'll have to think of a way to make
it into a format that people will be able to read easily for the monthly
report. Maybe we could do a TL;DR section at the top with just a
shortened bullet-list of important stuff and then a longer section with
the bug numbers and descriptions? Or maybe just a short list with
references to the bugs? e.g.:
TL;DR
* Stopped collecting user e-mail address and Fennec crash reports
* Improved crash report preview and raw views
* GPU names are now always up-to-date
* ...
Long story:
* As part of our efforts to reduce the amount of data we gather from
users we removed e-mail addresses from crash reports. This included
purging the e-mail from reports still containing it and removing all the
bits in Firefox that were used to collect them (bug X, Y and Z).
* ...
What do you think?
Gabriele
On 02/04/21 15:44, William Kahn-Greene wrote:
> Picking beginning of March as the beginning of the time frame....
>
> * What's your team/project?
> o Crash ingestion pipeline: Socorro and Tecken.
> * What did you accomplish? (Descriptions, bug numbers, etc)
> o Improved the preview in Slack/Matrix for crash report view urls
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1688203>
> o End collection of Email data in crash reports.
> + I changed the collector to delete Email data for all
> their help with this!
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1688883
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1688883>
> o End collection of crash reports for Fennec
> + When working on ending collection of Email data, it came up
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1699239
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1699239>
> o Fixed the webapp to automatically update the PCI device db once
> a week.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1166058
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1166058>
> o Redid the "Raw data and minidumps tab in the crash report view
> of the webapp.
> + The Crash Stats ui is confusing and clunky and I've been
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1696910>
> o New symbolication API microservices
> + The symbolication API that Tecken has is hard to improve and
> https://symbolication.stage.mozaws.net/symbolicate/v5
> <https://symbolication.stage.mozaws.net/symbolicate/v5>
> + I need to write docs for it, but it uses the same payload as
> <https://tecken.readthedocs.io/en/latest/symbolication.html#symbolication-symbolicate-v5>
> + If you do any symbolication work, I'd love to know how it
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1636210>
> * What are you working on now or think you'll have done this month?
> (Descriptions, bug numbers, etc)
> o Finishing up the new symbolication API microservice:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1636210
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1636210>
> o Crash Stats fixes
> o (Back burner): Better Java crash report signature generation:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1541120
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1541120>
> * What do you need help with?
> o Testing the new symbolication API. If you do anything with
> You received this message because you are subscribed to the Google
> Groups "crash-reporting-wg" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crash-reporting...@mozilla.com
> <mailto:crash-reporting...@mozilla.com>.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qjOg%2BaW%2Bwk9%2BFsTNYLYAiNfhqKWcL8cLs9MCTDrZyFZmg%40mail.gmail.com
> <https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qjOg%2BaW%2Bwk9%2BFsTNYLYAiNfhqKWcL8cLs9MCTDrZyFZmg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/a/mozilla.com/d/optout
> <https://groups.google.com/a/mozilla.com/d/optout>.
(from me, Kris, Alexis and Calixte) we'll have to think of a way to make
it into a format that people will be able to read easily for the monthly
report. Maybe we could do a TL;DR section at the top with just a
shortened bullet-list of important stuff and then a longer section with
the bug numbers and descriptions? Or maybe just a short list with
references to the bugs? e.g.:
TL;DR
* Stopped collecting user e-mail address and Fennec crash reports
* Improved crash report preview and raw views
* GPU names are now always up-to-date
* ...
Long story:
* As part of our efforts to reduce the amount of data we gather from
users we removed e-mail addresses from crash reports. This included
purging the e-mail from reports still containing it and removing all the
bits in Firefox that were used to collect them (bug X, Y and Z).
* ...
What do you think?
Gabriele
On 02/04/21 15:44, William Kahn-Greene wrote:
> Picking beginning of March as the beginning of the time frame....
>
> o Crash ingestion pipeline: Socorro and Tecken.
> * What did you accomplish? (Descriptions, bug numbers, etc)
> o Improved the preview in Slack/Matrix for crash report view urls
> and signature report view urls.
> + If there's more I can do with this to make these url
> previews more helpful in conversations, let me know.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1688203
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1688203>
> o End collection of Email data in crash reports.
> + I changed the collector to delete Email data for all
> incoming crash reports. I fixed the Firefox main and content
> crash reporter client code. I still have some changes to
> make in the webapp, but I'm waiting until May 2021 to do that.
> + Many thanks to Emily, Nneka, Gabriele, Mike, and Chris for
> crash reporter client code. I still have some changes to
> make in the webapp, but I'm waiting until May 2021 to do that.
> their help with this!
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1688883
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1688883>
> o End collection of crash reports for Fennec
> + When working on ending collection of Email data, it came up
> that we don't need Fennec crash reports anymore. Thus
> Socorro now rejects all incoming crash reports for Fennec.
> + Many thanks to Emily, Stefan, Vesta, and Agi!
> Socorro now rejects all incoming crash reports for Fennec.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1699239
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1699239>
> o Fixed the webapp to automatically update the PCI device db once
> a week.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1166058
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1166058>
> o Redid the "Raw data and minidumps tab in the crash report view
> of the webapp.
> + The Crash Stats ui is confusing and clunky and I've been
> trying to fix bits of it over time. In this pass, I improved
> the tab that holds links to raw and processed crash data,
> minidumps, and the output of minidump-stackwalk. It should
> be clearer now as to what's protected data and what isn't.
> The links are at the top of the tab where they're easier to
> access. The minidump-stackwalk output is much easier to
> manipulate and use.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1696910
> the tab that holds links to raw and processed crash data,
> minidumps, and the output of minidump-stackwalk. It should
> be clearer now as to what's protected data and what isn't.
> The links are at the top of the tab where they're easier to
> access. The minidump-stackwalk output is much easier to
> manipulate and use.
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1696910>
> o New symbolication API microservices
> + The symbolication API that Tecken has is hard to improve and
> there are a bunch of things we want to do with it. Because
> of that, I embarked on splitting it out into a separate
> microservice and rewriting it from the ground up using the
> Symbolic library. That's taken a while for a variety of
> reasons, but we've now got a working symbolication API in
> our staging environment that I think is usable.
> + API url:
> of that, I embarked on splitting it out into a separate
> microservice and rewriting it from the ground up using the
> Symbolic library. That's taken a while for a variety of
> reasons, but we've now got a working symbolication API in
> our staging environment that I think is usable.
> https://symbolication.stage.mozaws.net/symbolicate/v5
> <https://symbolication.stage.mozaws.net/symbolicate/v5>
> + I need to write docs for it, but it uses the same payload as
> the existing symbolication API as documented here:
> + https://tecken.readthedocs.io/en/latest/symbolication.html#symbolication-symbolicate-v5
> <https://tecken.readthedocs.io/en/latest/symbolication.html#symbolication-symbolicate-v5>
> + If you do any symbolication work, I'd love to know how it
> works for you and whether you encounter any issues.
> + https://bugzilla.mozilla.org/show_bug.cgi?id=1636210
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1636210>
> * What are you working on now or think you'll have done this month?
> (Descriptions, bug numbers, etc)
> o Finishing up the new symbolication API microservice:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1636210
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1636210>
> o Crash Stats fixes
> o (Back burner): Better Java crash report signature generation:
> https://bugzilla.mozilla.org/show_bug.cgi?id=1541120
> <https://bugzilla.mozilla.org/show_bug.cgi?id=1541120>
> * What do you need help with?
> o Testing the new symbolication API. If you do anything with
> symbolication, please let me know.
>
>
>
> /will
>
>
> On Thu, Apr 1, 2021 at 3:43 PM William Kahn-Greene <wil...@mozilla.com
> <mailto:wil...@mozilla.com>> wrote:
>
> Hi!
>
> If you work on crash reporting related things or a crash reporting
> related project, please reply to this email before Tuesday, April
> 6th if you have status updates. Short with outlines is fine. Long is
> fine. If you already have some kind of status newsletter, feel free
> to reply with a link to that. I'll take all these replies and
> compile a newsletter update thing.
>
> I want to do something like this every month. This is the first
> month, so we'll learn something about this time around and maybe
> change it next time around.
>
> /will
>
>
> Questions:
>
> What's your team/project?
>
> What did you accomplish? (Descriptions, bug numbers, etc)
>
> What are you working on now or think you'll have done this month?
> (Descriptions, bug numbers, etc)
>
> What do you need help with?
>
> What are you concerned about?
>
> What else do you think is helpful for everyone to know?
>
>
> --
>
>
>
> /will
>
>
> On Thu, Apr 1, 2021 at 3:43 PM William Kahn-Greene <wil...@mozilla.com
> <mailto:wil...@mozilla.com>> wrote:
>
> Hi!
>
> If you work on crash reporting related things or a crash reporting
> related project, please reply to this email before Tuesday, April
> 6th if you have status updates. Short with outlines is fine. Long is
> fine. If you already have some kind of status newsletter, feel free
> to reply with a link to that. I'll take all these replies and
> compile a newsletter update thing.
>
> I want to do something like this every month. This is the first
> month, so we'll learn something about this time around and maybe
> change it next time around.
>
> /will
>
>
> Questions:
>
> What's your team/project?
>
> What did you accomplish? (Descriptions, bug numbers, etc)
>
> What are you working on now or think you'll have done this month?
> (Descriptions, bug numbers, etc)
>
> What do you need help with?
>
> What are you concerned about?
>
> What else do you think is helpful for everyone to know?
>
>
> You received this message because you are subscribed to the Google
> Groups "crash-reporting-wg" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crash-reporting...@mozilla.com
> <mailto:crash-reporting...@mozilla.com>.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qjOg%2BaW%2Bwk9%2BFsTNYLYAiNfhqKWcL8cLs9MCTDrZyFZmg%40mail.gmail.com
> <https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qjOg%2BaW%2Bwk9%2BFsTNYLYAiNfhqKWcL8cLs9MCTDrZyFZmg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
> For more options, visit https://groups.google.com/a/mozilla.com/d/optout
> <https://groups.google.com/a/mozilla.com/d/optout>.
Gabriele Svelto
Apr 5, 2021, 3:35:23 PM4/5/21
to William Kahn-Greene, crash-reporting-wg
I went over what I did this month and it's largely been work on
integrating Windows Error Reporting in Firefox. The work hasn't landed
so maybe it's not worth announcing it just yet.
> <https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qhrJqcpsprxEzBzYgsqTQgsFE_LBkR5wiMGa1nzKon%3DQA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
integrating Windows Error Reporting in Firefox. The work hasn't landed
so maybe it's not worth announcing it just yet.
> --
> You received this message because you are subscribed to the Google
> Groups "crash-reporting-wg" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crash-reporting...@mozilla.com
> <mailto:crash-reporting...@mozilla.com>.
> To view this discussion on the web visit
> https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qhrJqcpsprxEzBzYgsqTQgsFE_LBkR5wiMGa1nzKon%3DQA%40mail.gmail.com
> You received this message because you are subscribed to the Google
> Groups "crash-reporting-wg" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to crash-reporting...@mozilla.com
> <mailto:crash-reporting...@mozilla.com>.
> To view this discussion on the web visit
> <https://groups.google.com/a/mozilla.com/d/msgid/crash-reporting-wg/CAKnh9qhrJqcpsprxEzBzYgsqTQgsFE_LBkR5wiMGa1nzKon%3DQA%40mail.gmail.com?utm_medium=email&utm_source=footer>.
William Kahn-Greene
Apr 7, 2021, 1:47:01 PM4/7/21
to crash-reporting-wg
I compiled the newsletter and sent it to firefox-dev and dev-platform. I also added a section to the wiki and put it there:
Thanks!
/will
Reply all
Reply to author
Forward
0 new messages