getsentry/sentry — pull request #944 by dmk23 (2013-07-20 02:38:38+00:00)
Title: Calculate composite hash from all interfaces plus message

I made a patch to solve one of the problems noted here: https://github.com/getsentry/sentry/issues/889

The problem with the old behavior is that only one interface (or the message, if no interfaces have a hash) determines the hash of the event. That behavior is very dangerous because the order of interface iteration is not guaranteed and it is not always desirable to have any interface nullify the impact of the message on the hash.

For example we have a requirement where multiple loggers representing different customers could generate the same stacktrace (same interface hash) which we would nonetheless want to be grouped into different groups per customer (which are identified in the message contents).

The solution is trivial, make sure every interface along with the message contributes to the hash.

This has been tested & deployed internally, so should be safe to merge.