In https://github.com/getsentry/sentry/pull/80935, we switched from calculating fingerprinting rule text in the expose_fingerprint_dict helper to reading it from the fingerprint info, since as of https://github.com/getsentry/sentry/pull/79231 we store it there. This works fine for new events, but this code also runs when someone opens the grouping info section of the issue details page, and if they do that on an event from before we started storing the rule text, it results in a key error.
This fixes that by partially undoing the change made in https://github.com/getsentry/sentry/pull/80935 - it doesn't switch back to always re-calculating the the rule text, but does fall back to doing so when it's not found in the stored data.
In https://github.com/getsentry/sentry/pull/80935, we switched from calculating fingerprinting rule text in the
expose_fingerprint_dicthelper to reading it from the fingerprint info, since as of https://github.com/getsentry/sentry/pull/79231 we store it there. This works fine for new events, but this code also runs when someone opens the grouping info section of the issue details page, and if they do that on an event from before we started storing the rule text, it results in a key error.This fixes that by partially undoing the change made in https://github.com/getsentry/sentry/pull/80935 - it doesn't switch back to always re-calculating the the rule text, but does fall back to doing so when it's not found in the stored data.