f84af74a7c
Remove hard-coded webhook_url from test_message
...
as pointed out by Slack's own bots
2025-06-11 08:42:06 +02:00
b53b1c6ce2
1.6.0 CHANGELOG
2025-06-10 22:32:12 +02:00
fac5b19966
Slack Alerts
...
Fix #3
2025-06-10 22:00:37 +02:00
33d5865579
Clarifying comments on logmessage display
2025-06-03 15:47:46 +02:00
5d316332d0
Display formatted log message when available
...
Fix #111
2025-06-03 15:44:36 +02:00
6822ec0194
Add 2 env variables to compose-sample.yaml
...
See #110
2025-06-03 15:31:02 +02:00
462b4f131a
Merge pull request #108 from bugsink/hijacked-pr-84
...
feat: add delete functionality for users
2025-05-29 17:21:53 +02:00
febcabc9f3
feat: add delete functionality for users
...
Implement delete functionality with confirmation modals for users. Ensure
proper authorization checks are in place before deletion. Add corresponding
JavaScript files to handle modal interactions and form submissions.
Based on #84
Signed-off-by: Animesh Agrawal <animesh@flick2know.com >
2025-05-29 17:14:54 +02:00
da77957870
in development: env-level configuration of the NPM_BIN_PATH
...
As asked by @anime-shed on #78
2025-05-29 16:51:45 +02:00
4c104714e3
Fix the tests
...
update key phrases according to the recent improvements;
specifically: test also for the fact that function-name now shows up
See #87
2025-05-29 11:11:45 +02:00
ef5c203d78
Merge branch 'sourcemaps-multi-source-test'
2025-05-29 11:01:37 +02:00
1a60cbcd3c
Add test for multi-file sourcemaps
...
See #87 for the code that fixes this
2025-05-29 11:01:10 +02:00
a835449bef
flake8
2025-05-28 22:24:19 +02:00
46c9f3d7cc
Merge pull request #87 from bpeschier/fix/sourcemap-with-multiple-sources
...
* Apply source mapping when sourcemap contains multiple sources
* Propagate `filename` and `function` from the sourcemap.
2025-05-28 22:18:02 +02:00
f817b3ba2f
Lookup by debug_id in dicts: use UUID
...
in absence of a clean reproducer, just doing proper lookups on a
normalized thing seems the more stable thing to do.
Fix #105 (in absence of test: I think)
2025-05-28 22:03:51 +02:00
859ba6b31e
Add test that proves database lookups on UUID work the way you think
...
See #105
2025-05-28 22:02:35 +02:00
9375dbc140
Merge pull request #107 from bugsink/dependabot/pip/python-packages-a9558a5c6c
...
Update sentry-sdk and jsonschema
2025-05-27 20:18:52 +02:00
8544a47e8c
Bump the python-packages group across 1 directory with 2 updates
...
Updates the requirements on [sentry-sdk](https://github.com/getsentry/sentry-python ) and [jsonschema](https://github.com/python-jsonschema/jsonschema ) to permit the latest version.
Updates `sentry-sdk` to 2.29.1
- [Release notes](https://github.com/getsentry/sentry-python/releases )
- [Changelog](https://github.com/getsentry/sentry-python/blob/master/CHANGELOG.md )
- [Commits](https://github.com/getsentry/sentry-python/compare/2.27.0...2.29.1 )
Updates `jsonschema` to 4.24.0
- [Release notes](https://github.com/python-jsonschema/jsonschema/releases )
- [Changelog](https://github.com/python-jsonschema/jsonschema/blob/main/CHANGELOG.rst )
- [Commits](https://github.com/python-jsonschema/jsonschema/compare/v4.23.0...v4.24.0 )
---
updated-dependencies:
- dependency-name: sentry-sdk
dependency-version: 2.29.1
dependency-type: direct:production
dependency-group: python-packages
- dependency-name: jsonschema
dependency-version: 4.24.0
dependency-type: direct:production
dependency-group: python-packages
...
Signed-off-by: dependabot[bot] <support@github.com >
2025-05-27 15:54:19 +00:00
ab7ad72376
Default worker-count in Docker: min(cpu_count, 4) instead of 1
...
As per discussion with @sekrause on #101
Briefly: recent reduction is a good idea, but 1 is probably too
little.
2025-05-18 11:18:54 +02:00
b58058ccd1
Repeatable tests/fix CI/CD
...
fixes KeyError: "exception"
2025-05-18 09:48:21 +02:00
9770711823
Add robots.txt that disallows crawling
...
There's not much to crawl, but if you're running Bugsink somewhere
and search engines 'somehow find out about it', you generally probably
don't want randos on the internet to find that
2025-05-18 09:33:43 +02:00
7f2e4b786b
Default worker-count in Docker: 1 instead of 10
...
My reasoning is twofold:
1. a count of 1 is actually probably "enough for many setups" because ingestion
is very fast anyway (just store the file); while the lower memory-footprint
that comes with having fewer workers means that adoption of Bugsink will be
easier.
2. tuning the variable is going to be less annoying if there's no default that
might override "in the wrong direction" (i.e. the interaction between
`WEB_CONCURRENCY` and `GUNICORN_CMD_ARGS`)
See #101 (where the concept of customizability was discussed, though not the
present idea of chaning the default).
2025-05-18 09:15:43 +02:00
ef630ded50
Make number of Gunicorn workers configurable in Docker setup
...
Fix #101
It becomes configurable by passing an environment-var someting like so
to your `docker run` (or equivalent).
GUNICORN_CMD_ARGS="--workers=123"
2025-05-17 22:17:28 +02:00
232d2d969d
Add HEALTHCHECK command to Dockerfile*
...
See #98
2025-05-15 16:38:48 +02:00
430b130a94
Fingerprint: convert to string before concatenating
...
Fixes #102 ; as discussed in that issue: although such fingerprints are not
up-to-spec the sentry docs directly recommend them, and it would be nice
to not crash on them
2025-05-12 15:54:29 +02:00
66ec55937c
Even more clear "don't touch this DB" warning
2025-05-12 13:53:02 +02:00
4743e75019
Add /health/ready endpoint
...
Fixes #98
2025-05-12 13:42:57 +02:00
78a95fb493
Add another note about SNAPPEA db
...
this time about the path
2025-05-12 13:26:32 +02:00
4de7bfe1df
1.5.4 CHANGELOG
2025-05-12 10:59:08 +02:00
2b8efc9452
stress_test command: remove must-be-true fresh-id param
2025-05-12 10:56:39 +02:00
528998fae5
stress_test command: remove deprecated 'use_envelope' option
...
we always do that, as per the now-removed comment
2025-05-12 10:49:06 +02:00
ab3e6da582
build_dsn: add assertion
...
like the systemcheck from 0c14962d92
2025-05-12 10:43:53 +02:00
265a3e56ee
Textual: setting-name in all-caps
2025-05-12 10:42:53 +02:00
6b4fac0f86
Show _all_ Request Headers in CSRF_DEBUG view
...
the less relevant ones grayed out
This may help in debugging #100
2025-05-12 10:31:12 +02:00
0c14962d92
Add system-check for BASE_URL
2025-05-10 14:01:43 +02:00
3f43981475
Fix (obj not found) when visiting project as a superuser
...
project of which you're not a member
2025-05-09 16:47:21 +02:00
4bd1ed7fa4
send_json command doesn't depend on settings either
2025-05-09 12:51:47 +02:00
66899c5144
Add bugsink-util script to allow settings-independent commands to be run
2025-05-09 12:49:34 +02:00
8b8c56914c
1.5.3 CHANGELOG
2025-05-07 21:50:33 +02:00
9b0f0e04f4
CREATE_SUPERUSER shortcut: robust for ':' in password
2025-05-07 09:21:21 +02:00
0dfd01db9b
Performance: don't evaluate all project issues to show/hide checkbox
...
Doing so is expensive (to the point of timeout) for largish numbers
of issues.
2025-05-06 23:01:09 +02:00
aad0f624f9
Fix: issue-list indexes must have project first
...
because we always filter by project before ordering;
the now-removed first_seen index was simply unused
2025-05-06 22:19:31 +02:00
699f6e587d
fix: _get_runtime_limit must apply to the right alias
...
instead of just returning the value for the default alias
that this wasn't done was a bug generally (the per-alias limits
simply didn't apply) but was exposed when running the CI against
non-sqlite databases, because in that setup the main database
would not get a limit set, but because the getter fell back
to the default (which wasn't set) there was an exception.
2025-05-06 21:45:41 +02:00
474c677f12
limit_runtime: log non-interruptions
2025-05-06 16:57:06 +02:00
b33d559d44
1.5.2 CHANGELOG
2025-05-06 12:55:06 +02:00
49e6700d4a
Grouping.grouping_key: hash it for the index
2025-05-06 11:32:19 +02:00
d5a449020d
Stress test: more fat-tailed randomness
...
direct cause: the ability to create test-data for many-Issue setups
2025-05-06 10:42:18 +02:00
cc2b22f08e
Digest: check Grouping.exists only once (save a query)
2025-05-06 10:30:51 +02:00
17fb9cc850
Remove open_issue_count from homepage; it's too expensive
2025-05-06 10:27:16 +02:00
3783661054
Issue Paginator: don't attempt to count the Issues
...
Counting incurs looking at all records which is too expensive if you have e.g.
1_000_000 issues.
Note that we take a different approach than the one for Events (where we
count-with-timeout). Reason for switching:
https://sqlite.org/forum/forumpost/fa65709226
For Events we have a known count for the non-query case (denormalized/counted
value), so we preserve what we had there. For Issues the trouble of keeping
counts right for muted/etc. is not (currently) worth it.
2025-05-06 10:13:06 +02:00
Klaas van Schelven