-
Notifications
You must be signed in to change notification settings - Fork 104
Better choices for stackTraceKey
#1310
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
Conversation
c572042
to
ee6c2ef
Compare
|
Actually that kotlin reflection thing is pretty bad, the type is the only unique bit. |
Ah, but the redacted bit had a very nice name. Okay, I think this will work. Going to look a bit harder to see if I can get the "Kotlin reflection" noise out of there, every time it shows up is irritating. |
No wait, that's in the message, not the stack key. So the stack key should be using whatever is in the message… |
That's the |
ee6c2ef
to
432800b
Compare
|
Ah, bliss!
|
432800b
to
926da97
Compare
Bah, backing out the reflection tweak b/c of a broken unit test, |
6d76e25
to
ae2840d
Compare
Found a few spots where `stackTraceKey` was including id hashes, resulting in separate crash reporter error groups per process. Fixed that and over-documented the rules. Glad this isn't public API.
ae2840d
to
22432fa
Compare
Found a better spot for |
Found a few spots where
stackTraceKey
was including id hashes, resulting in separate crash reporter error groups per process. Fixed that and over-documented the rules. Glad this isn't public API.