Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix tests to respond to Python 3.12 handling of utcnow in sentry-sdk #34946

Merged
merged 1 commit into from
Oct 14, 2023

Commits on Oct 14, 2023

  1. Fix tests to respond to Python 3.12 handling of utcnow in sentry-sdk

    The sentry-sdk 1.32.0 released on 11th of October fixed handling of
    utcnow to make it future-compatible with Python 3.12. The breadcrumb
    timestamp returned was naive and now it is timezone aware with
    utc specified explicitly as timezone. This broke our tests.
    
    The change in sentry that impacted it is
    getsentry/sentry-python#2415
    
    We use the opportunity also to bump sentry sdk minimum version
    to be 1.32.0 from very old 0.8.0 (from 2019). Sentry is a service, so
    they generally always want you to use the latest version, and sentry has
    very little requirements on its own to cause conflicts (for Python
    3.8+ it only requires "certifi" without any specific limitations)
    potiuk committed Oct 14, 2023
    Configuration menu
    Copy the full SHA
    451f78b View commit details
    Browse the repository at this point in the history