-
Notifications
You must be signed in to change notification settings - Fork 556
Comparing changes
Open a pull request
base repository: getsentry/sentry-python
base: 2.28.0
head repository: getsentry/sentry-python
compare: 2.29.1
- 12 commits
- 16 files changed
- 6 contributors
Commits on May 12, 2025
-
getsentry-bot committed
May 12, 2025 Configuration menu - View commit details
-
Copy full SHA for 0c95a73 - Browse repository at this point
Copy the full SHA 0c95a73View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1090eee - Browse repository at this point
Copy the full SHA 1090eeeView commit details
Commits on May 13, 2025
-
fix(logs): Make
sentry.message.parameters
singular as per spec (#4387)As per https://develop.sentry.dev/sdk/telemetry/logs/#default-attributes we should be using `sentry.message.parameter` (singular) instead of `sentry.message.parameters`. This matches how we approach the other attributes in our conventions.
Configuration menu - View commit details
-
Copy full SHA for eee4cac - Browse repository at this point
Copy the full SHA eee4cacView commit details
Commits on May 15, 2025
-
ci: Fix pyspark test suite (#4382)
- pyspark was failing to bind to an address - aws_lambda fixed itself 🪄
Configuration menu - View commit details
-
Copy full SHA for c639f1c - Browse repository at this point
Copy the full SHA c639f1cView commit details -
Configuration menu - View commit details
-
Copy full SHA for aa0eaab - Browse repository at this point
Copy the full SHA aa0eaabView commit details
Commits on May 19, 2025
-
fix(celery): Do not send extra check-in (#4395)
When using the RedBeatScheduler, we're sending an extra in-progress check-in at scheduler start. Since this is never followed by an ok or error check-in, the check-in is marked as timed out in Sentry. We're patching the scheduler's `maybe_due`, which (as the name implies) [might not end up executing the task](https://github.com/sibson/redbeat/blob/bdefad23b47f75e2e85d45f46f9f16dd00a93d40/redbeat/schedulers.py#L506-L508). This is indeed what seems to be happening -- `maybe_due` is run when the scheduler starts, but without scheduling the task. We don't check whether `maybe_due` actually ended up scheduling anything and always fire an in-progress check-in. Patching the [scheduler's `apply_async`](https://github.com/sibson/redbeat/blob/bdefad23b47f75e2e85d45f46f9f16dd00a93d40/redbeat/schedulers.py#L511) instead. Closes #4392
Configuration menu - View commit details
-
Copy full SHA for 2f97cda - Browse repository at this point
Copy the full SHA 2f97cdaView commit details -
feat: Allow configuring
keep_alive
via environment variable (#4366)This commit enables the `keep_alive` option to be set via the `SENTRY_KEEP_ALIVE` environment variable. When both the environment variable and the argument are provided, the argument takes precedence. Closes #4354
Configuration menu - View commit details
-
Copy full SHA for f572757 - Browse repository at this point
Copy the full SHA f572757View commit details -
fix(loguru): Move integration setup from
__init__
tosetup_once
(#……4399) We shouldn't have setup code in an integration's `__init__`. This can be called an arbitrary amount of times. `setup_once` exists so that the code is only guaranteed to run once. Having integration setup in `__init__` also means that the integration currently can't be disabled via `disabled_integrations`. Fixes #4398
Configuration menu - View commit details
-
Copy full SHA for 830f270 - Browse repository at this point
Copy the full SHA 830f270View commit details -
Configuration menu - View commit details
-
Copy full SHA for 0c9333e - Browse repository at this point
Copy the full SHA 0c9333eView commit details -
getsentry-bot committed
May 19, 2025 Configuration menu - View commit details
-
Copy full SHA for 8be519f - Browse repository at this point
Copy the full SHA 8be519fView commit details -
fix(logs): send
severity_text
:warn
instead ofwarning
(#4396)We need to send `warn` as the `severity_text` for warning level logs, not `warning`. If we send `warning` it will not be recognized by the backend and the severity will show up as `UNKNOWN` in the frontend. See screenshot for comparison of after and before. 
Configuration menu - View commit details
-
Copy full SHA for 3ebd122 - Browse repository at this point
Copy the full SHA 3ebd122View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7973ac0 - Browse repository at this point
Copy the full SHA 7973ac0View commit details
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff 2.28.0...2.29.1