Klaas van Schelven
a00a815261
Merge branch 'main' into tag-search
2025-03-03 15:02:13 +01:00
Klaas van Schelven
70b77d71ee
Fix conditional on 'Issue Tags' RHS
2025-03-03 13:42:36 +01:00
Klaas van Schelven
bbfee84c6a
issue tags: single query rather than one-per-tag
2025-03-03 13:42:18 +01:00
Klaas van Schelven
e6bc660731
Add note about per-key tag pages
2025-03-03 13:25:41 +01:00
Klaas van Schelven
1ae5bb3fd1
Tags: no cutoff when there are many
...
this idea was superceded by doing it explicitly in 00c49443eb
2025-03-03 13:23:52 +01:00
Klaas van Schelven
5930740e0b
Tags: as a separate tab
2025-03-03 12:56:20 +01:00
Klaas van Schelven
c8ecf508de
Tags: on event details page show calculated tags
...
(not just the explicitly provided ones)
2025-03-03 11:29:07 +01:00
Klaas van Schelven
124f90b403
'Issue Tags' box: show on all issue-related pages
...
now that it's no longer tied to the event...
2025-03-03 11:00:11 +01:00
Klaas van Schelven
406472b6d4
os.version as a tag
2025-03-03 10:55:15 +01:00
Klaas van Schelven
33ed3242c2
Fix browser.version tag-deduction
2025-03-03 10:54:17 +01:00
Klaas van Schelven
00c49443eb
Add 'mostly_unique' property to tags
2025-03-03 10:52:28 +01:00
Klaas van Schelven
1b9a76bc17
Add comment about counting tags occurrences
2025-03-03 09:41:00 +01:00
Klaas van Schelven
d400d98a02
Add setting to enable opting out of PHONEHOME
...
Fixes #52
2025-03-03 09:26:06 +01:00
Klaas van Schelven
1571a4f87f
Linebreaks in event detail values
...
Prompted by .message; but more generally useful and applied.
Fixes #51
2025-03-03 09:12:06 +01:00
Klaas van Schelven
adf92f6b1b
make_consistent: update has_releases when needed
...
See #50
2025-03-03 09:06:31 +01:00
Klaas van Schelven
60920b7299
fix 'n total observed' at top of event-list page
...
this was showing the project's count since 336e126e3e , i.e. since
it was introduced
2025-02-28 11:29:21 +01:00
Klaas van Schelven
7a30de3840
Issue Tags: select_related
2025-02-28 10:09:53 +01:00
Klaas van Schelven
60e25dac42
Issue Tags display: 'Other', sorting (WIP)
2025-02-28 09:48:01 +01:00
Klaas van Schelven
2c444c6e80
Display Issue (not event) tags in the RHS detail; WIP
2025-02-28 09:33:58 +01:00
Klaas van Schelven
f7e85b788c
Tags: count at issue-level (model impl. only)
2025-02-27 21:58:14 +01:00
Klaas van Schelven
4404538893
Storing tags in the DB: use bulk_create; a few tests
2025-02-27 20:41:36 +01:00
Klaas van Schelven
89d53a15c9
digest_tags: just use project_id to avoid lookups
...
maybe maybe the passed-in event also avoids this, but the present
method will always do what you expect and this is obvious upon
reading, rather than have the reader think about something
2025-02-27 16:21:29 +01:00
Klaas van Schelven
d5228f9932
Add 'level' to logentry event details
2025-02-27 15:26:10 +01:00
Klaas van Schelven
e10c1bf7ca
Remove 'store_events' command
...
this command to store all events on the local filesystem was useful
while 'scaffolding'; getting my hands on some initial event-data in
the early days of Bugsink, but it was never meant as a permanent tool
2025-02-27 15:14:05 +01:00
Klaas van Schelven
0d4d95defd
Use .iterator() idiom in init_tags
...
to avoid loading all events into memory before looping over them
There's some warnings in the docs about SQLite and iterators, but
I don't think those apply, for one because we don't write to the
events: https://docs.djangoproject.com/en/5.1/ref/databases/#sqlite-isolation
2025-02-27 14:54:26 +01:00
Klaas van Schelven
ab961d81c1
init_tags: interruptable; show progress
2025-02-27 14:35:59 +01:00
Klaas van Schelven
0aa067eb9b
Add --fresh-trace and --tag params to send_json/stress_test
2025-02-27 14:04:52 +01:00
Klaas van Schelven
5f1d5832d1
Add 'init_tags' command
2025-02-27 13:36:17 +01:00
Klaas van Schelven
ef3b19d794
UI: Specific 'no issues found' when searching
2025-02-27 13:18:33 +01:00
Klaas van Schelven
7a19e2d277
Tags; deducing tags; search on tags; WIP
2025-02-27 13:12:49 +01:00
Klaas van Schelven
4b7ed8f4ec
Rename get_contexts_enriched_with_ua
...
more closely match what's going on
2025-02-26 18:20:52 +01:00
Klaas van Schelven
348c2dc80f
tox.ini rule, as per comment
...
the associated code got removed before checkin, but I still like to ignore this
rule in the future
2025-02-26 16:34:47 +01:00
Klaas van Schelven
70a26ebb0f
Typo in changelog
2025-02-24 11:40:10 +01:00
Klaas van Schelven
e876944d42
Add note to 1.3.0 CHANGELOG
2025-02-20 22:07:54 +01:00
Klaas van Schelven
14d34807ca
Snappea 'worker done': display task name
...
for the important case of 'quickly eye-balling what-took-you-so-long'
this saves those eye-balls a lookup
1.3.0
2025-02-20 21:38:14 +01:00
Klaas van Schelven
f6b2c8ffbf
1.3.0 CHANGELOG
2025-02-20 21:27:19 +01:00
Klaas van Schelven
af58c8174a
QuietConsoleEmailBackend: prettier printing
...
message more clear, subject on a single line
2025-02-20 15:46:59 +01:00
Klaas van Schelven
757ee31bed
Support for CORS
...
Tested in-browser with:
```
function main() {
$.ajax({
type: "POST",
url: "http://bugsink:8000/api/1/store/ ",
headers: {
"Content-Type": "application/json",
"X-Sentry-Auth": "Sentry sentry_key=a2df4cd647dc4b7a8a81b78a3601eba1, sentry_version=7, sentry_client=bugsink/0.0.1",
},
data: JSON.stringify({foo: "Bar"}),
success: function(data) {
console.log(data);
}
});
}
```
2025-02-20 14:43:10 +01:00
Klaas van Schelven
2354241e2c
2 email backend warning improvements
...
*,Don't mention EMAIL_BACKEND in the warning message: in the
Docker setup, this isn't even a thing.
* In the single-server setup, when email is unconfigured, use
an explict Quiet backend. This will make sure you don't just
get failure-to-send, instead you'll get the nice yellow banner.
This will not affect existing setups (by design) because of
the template-based setup (those setups will have their version
already deployed)
2025-02-20 10:21:25 +01:00
Klaas van Schelven
387d037c7c
Slight rewording in the README
2025-02-20 09:29:57 +01:00
Klaas van Schelven
934764dd8c
Tests: Better error message for failing integration tests
2025-02-20 09:26:04 +01:00
Klaas van Schelven
93ae506230
Don't 'eat your own dogfood' (send errors) while running tests
...
this was generally already so, but as per issue 4078 at sentry-python, not in all cases
2025-02-19 21:31:37 +01:00
Klaas van Schelven
bc1541050d
thousand-separators for counts
...
useful when there are very many events
2025-02-19 16:58:54 +01:00
Klaas van Schelven
154dceb2af
EVENT_STORAGE (FileEventStorage): docker-configurable
2025-02-19 16:09:01 +01:00
Klaas van Schelven
b169749231
Send welcome email: as a command
2025-02-19 14:52:48 +01:00
Klaas van Schelven
073bc7aaec
make_consistent: add --dry-run
2025-02-19 12:06:16 +01:00
Klaas van Schelven
f4250d2db8
make_consistent: document possible way forward
2025-02-19 11:56:21 +01:00
Klaas van Schelven
92425890cd
make_consistent: take 'points to missing' into account while deleting
...
also: switch a number of deletions from in-the-loop deletions to
delete-using-sql.
2025-02-19 11:42:44 +01:00
Klaas van Schelven
918b1ef54c
Add ids to 2 system-checks
2025-02-18 12:10:32 +01:00
Klaas van Schelven
3cb07246b9
Add system-check for EVENT_STORAGES setting
2025-02-18 12:08:05 +01:00