Klaas van Schelven
b6b4083ac1
Move vendored code into explicitly licenced dir
2024-09-27 18:03:51 +02:00
Klaas van Schelven
390048e2cd
Comments/docstrings
2024-09-27 17:56:42 +02:00
Klaas van Schelven
d9e611ee9e
Remove a TODO
...
duplicate one-liner is fine
2024-09-17 10:05:15 +02:00
Klaas van Schelven
4dfefec468
denormalize/cache last_frame_* and transaction on Event and Issue
...
for performance, but also fixes:
* not just the 'last frame' but the 'last relevant frame' (in-app)
* truncation is properly done (matching the DB size, and for each of the fields)
2024-04-10 09:12:15 +02:00
Klaas van Schelven
f8d9aa736d
Push 'get_title' into default_issue_grouper
...
this is in prepartion of an expected future where we allow for more customization
of the grouping behavior
2024-04-08 16:30:11 +02:00
Klaas van Schelven
4016f13c07
Move truncatechars to the only place we actually need it
...
i.e. when storing stuff in the DB (other cases are taken care of on-render
2024-04-08 16:22:00 +02:00
Klaas van Schelven
652823f8c3
Store calculated type and value on issue and event and use these values in the templates
2024-04-08 15:30:41 +02:00
Klaas van Schelven
729a4c7ea1
Make <no transaction> explicit;
...
and more moving-around-of-code in preparation for our next step
2024-04-08 15:03:02 +02:00
Klaas van Schelven
cb75d318af
Remove the event_type_name from the grouper
...
it adds very little, especially now that we've put this information in the type
('Log Message') and removing this allows us to refactor more freely
2024-04-08 14:52:09 +02:00
Klaas van Schelven
a70ac7e1cb
Factor out the idea (exception -> type_, value) what we have
2024-04-08 14:39:14 +02:00
Klaas van Schelven
48307daa0f
Introduce 'Grouping' data-modeling
2024-04-08 11:41:15 +02:00
Klaas van Schelven
9dfae5a829
Use the diamond-separator when generating fingerprint-based groupers too
2024-04-05 15:41:12 +02:00
Klaas van Schelven
54e8009e73
Reorganize/cleanup title-generating code for clarification
2024-04-05 15:37:24 +02:00
Klaas van Schelven
80919d01b8
Remove the concept of 'culprit' from the grouping code
...
This has been deprecated in Sentry in 2016; no reason for us to support it.
It is noted that despite the deprecation (in favor of `transaction`) an
explicitly provided culprit actually took a higher precedence than an
explicitly provided transaction in the now-removed code.
2024-04-05 15:02:56 +02:00
Klaas van Schelven
2011006e74
Remove 'TODO' that was apparently already acted on
2024-04-05 11:13:08 +02:00
Klaas van Schelven
99b66ab472
Mutiple resolve/mute/... from UI: use querysets
2024-03-20 19:32:41 +01:00
Klaas van Schelven
28bf2f383e
Store fixed_at/events_at newline-terminated
...
easier to do 'contains' on later
2024-03-20 19:12:30 +01:00
Klaas van Schelven
d5e9aa07ca
Issue.fixed_at and Issue.events_at: bracketless
...
for easier qs-based updates (later/soon)
2024-03-20 17:42:59 +01:00
Klaas van Schelven
2dd3a23f5a
Add separator to issue_grouper for better human readability
2023-11-08 22:25:30 +01:00
Klaas van Schelven
b8b65b1ea6
Add visibility (debugability) to issue_grouper concept
2023-11-08 22:22:18 +01:00
Klaas van Schelven
fc7e186918
getting hash for issue: use GlitchTip's approach as an early stand-in
...
af9a700a8706f20771b005804d8c92ca95c8b072 in GlitchTip
2023-11-04 22:14:39 +01:00
