Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: getsentry/sentry-python
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 2.28.0
Choose a base ref
...
head repository: getsentry/sentry-python
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 2.29.1
Choose a head ref
  • 12 commits
  • 16 files changed
  • 6 contributors

Commits on May 12, 2025

  1. Merge branch 'release/2.28.0'

    getsentry-bot committed May 12, 2025
    Configuration menu
    Copy the full SHA
    0c95a73 View commit details
    Browse the repository at this point in the history
  2. apidocs: Remove snowballstemmer pin (#4379)

    Fixed upstream
    sentrivana authored May 12, 2025
    Configuration menu
    Copy the full SHA
    1090eee View commit details
    Browse the repository at this point in the history

Commits on May 13, 2025

  1. 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.
    AbhiPrasad authored May 13, 2025
    Configuration menu
    Copy the full SHA
    eee4cac View commit details
    Browse the repository at this point in the history

Commits on May 15, 2025

  1. ci: Fix pyspark test suite (#4382)

    - pyspark was failing to bind to an address
    - aws_lambda fixed itself 🪄
    sentrivana authored May 15, 2025
    Configuration menu
    Copy the full SHA
    c639f1c View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    aa0eaab View commit details
    Browse the repository at this point in the history

Commits on May 19, 2025

  1. 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
    sentrivana authored May 19, 2025
    Configuration menu
    Copy the full SHA
    2f97cda View commit details
    Browse the repository at this point in the history
  2. 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
    szokeasaurusrex authored May 19, 2025
    Configuration menu
    Copy the full SHA
    f572757 View commit details
    Browse the repository at this point in the history
  3. fix(loguru): Move integration setup from __init__ to setup_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
    sentrivana authored May 19, 2025
    Configuration menu
    Copy the full SHA
    830f270 View commit details
    Browse the repository at this point in the history
  4. release: 2.29.0

    getsentry-bot committed May 19, 2025
    Configuration menu
    Copy the full SHA
    0c9333e View commit details
    Browse the repository at this point in the history
  5. Merge branch 'release/2.29.0'

    getsentry-bot committed May 19, 2025
    Configuration menu
    Copy the full SHA
    8be519f View commit details
    Browse the repository at this point in the history
  6. fix(logs): send severity_text: warn instead of warning (#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.
    
    ![Screenshot 2025-05-16 at 18 24
    50](https://github.com/user-attachments/assets/240e3c6d-0f68-49e8-b79b-a67ac0e8a5d4)
    lcian authored May 19, 2025
    Configuration menu
    Copy the full SHA
    3ebd122 View commit details
    Browse the repository at this point in the history
  7. release: 2.29.1

    getsentry-bot committed May 19, 2025
    Configuration menu
    Copy the full SHA
    7973ac0 View commit details
    Browse the repository at this point in the history
Loading