Skip to content
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

Error grouping feature request #14

Open
GoogleCodeExporter opened this issue Feb 3, 2016 · 1 comment
Open

Error grouping feature request #14

GoogleCodeExporter opened this issue Feb 3, 2016 · 1 comment

Comments

@GoogleCodeExporter
Copy link

When receiving multiple similar reports, it would be very beneficial to have 
them grouped.

One could do this by generating a signature by hashing various components of 
the stack trace:
 - The root exception class (ex: NullPointerException)
 - The "interesting" class (ex: org.example.SomeClass)
 - The line number of the "interesting" class
 - The app version

The "interesting" class is defined as either (in prioritized order):
 - The top class from the root that lies in same package as the application
 - The class just below the top exception

Ideas about signatures can be found in:
https://github.com/ACRA/acralyzer/issues/2
http://support.hockeyapp.net/kb/about-general-faq/how-does-hockeyapp-group-crash
es

Original issue reported on code.google.com by [email protected] on 13 Aug 2013 at 5:37

@GoogleCodeExporter
Copy link
Author

Interesting, though i don't have time to do this.

Anyone can do the work and submit changes?

Original comment by [email protected] on 26 Aug 2013 at 9:46

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant