[file_crash_bug] Drop the date for the first crash report #2237
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Contributor
|
Why isn't it accurate? |
Member
Author
It is based on the time range that we query (which is 2 months). If the crash is older, it will still say 2 months. We have a text to clarify that, but it still could be confusing more than helpful:
Soccoro has an API to provide the date when the crash signature was ever seen, I'm not sure if including that date will have any value. |
Contributor
Maybe you could ask some crash analysis experts? |
marco-c
approved these changes
Oct 5, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The date in the description is not accurate and could be confusing.
Checklist
to-be-announcedtag added if this is worth announcing