I got a working reducer with tests. When I went to test it on crash data, I hit a slew of issues where the data in the processed crash is the wrong type. Bug #1754035 covers schema problems related to the new stackwalker. I'm hitting problems with a lot of other fields, too. Examples: * `available_physical_memory` is an int in the processed crash, but defined as a `[string, null]` in the schema * `available_virtual_memory` is an int in the processed crash, but defined as a `[string, null]` in the schema * `safe_mode` is a bool in the processed crash, but defined as a [string, null] in the schema and has values `"0"` and `"1"` in `telemetry.socorro_crash` I'll fix the other fields in this bug and fix the issues related to the new stackwalker in bug #1754035.
Bug 1762271 Comment 4 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I got a working reducer with tests. When I went to test it on crash data, I hit a slew of issues where the data in the processed crash is the wrong type. Bug #1754035 covers schema problems related to the new stackwalker. I'm hitting problems with a lot of other fields, too. Examples: * `available_physical_memory` is an int in the processed crash, but defined as a `[string, null]` in the schema * `available_virtual_memory` is an int in the processed crash, but defined as a `[string, null]` in the schema * `safe_mode` is a bool in the processed crash, but defined as a [string, null] in the schema and has values `"0"` and `"1"` in `telemetry.socorro_crash` We need to not break what's in `telemetry.socorro_crash`, so I'm going to write a converter to fix fields that need fixing as specified in the schema. I'll fix the other fields in this bug and fix the issues related to the new stackwalker in bug #1754035.