The `JavaException` annotation contains a structure that includes cascading exceptions. Bug #1698623 wants us to switch to the original "caused by" exception. However, I've never found out which way the array of exception values is sorted and which one that would be in the `java_exception` structure. This affects both signature generation and `generate_create_bug_url`. We should find a Fenix crash report with a `java_stack_trace` and a java_exception` and cascading exceptions so we can figure out which direction the array is sorted. After doing that, we should address the comment in the processed crash schema and note the sorting direction in the description: https://github.com/mozilla-services/socorro/blob/main/socorro/schemas/processed_crash.schema.yaml#L90-L91 After doing that, we should check signature generation and the `generate_create_bug_url` code to make sure they're using the correct exception value.
Bug 1888997 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The `JavaException` annotation contains a structure that includes cascading exceptions. Bug #1698623 wants us to switch to the original "caused by" exception. However, I've never found out which way the array of exception values is sorted and which one that would be in the `java_exception` structure. This affects both signature generation and `generate_create_bug_url`. We should find a Fenix crash report with a `java_stack_trace` and a java_exception` and cascading exceptions so we can figure out which direction the array is sorted. After doing that, we should address the comment in the processed crash schema and note the sorting direction in the description: https://github.com/mozilla-services/socorro/blob/main/socorro/schemas/processed_crash.schema.yaml#L90-L91 After doing that, we should check signature generation and the `generate_create_bug_url` code to make sure they're using the correct exception value and write up bugs if we find problems.