-
Notifications
You must be signed in to change notification settings - Fork 601
Comparing changes
Open a pull request
base repository: getsentry/sentry-python
base: 28d890a
head repository: getsentry/sentry-python
compare: a0ea6a9
- 13 commits
- 33 files changed
- 5 contributors
Commits on May 21, 2024
-
getsentry-bot committed
May 21, 2024 Configuration menu - View commit details
-
Copy full SHA for 7af75ce - Browse repository at this point
Copy the full SHA 7af75ceView commit details
Commits on May 22, 2024
-
fix(clickhouse):
_sentry_spanmight be missing (#3096)We started auto-enabling the ClickHouse integration in 2.0+. This led to it getting auto-enabled also for folks using ClickHouse with Django via `django-clickhouse-backend`, but it turns out that the integration doesn't work properly with `django-clickhouse-backend` and leads to `AttributeError: 'Connection' object has no attribute '_sentry_span'`.
Configuration menu - View commit details
-
Copy full SHA for 38c14e9 - Browse repository at this point
Copy the full SHA 38c14e9View commit details
Commits on May 23, 2024
-
Fix
coheretestsuite for new release ofcohere. (#3098)* Check for new class to signal end of stream
Configuration menu - View commit details
-
Copy full SHA for ec23396 - Browse repository at this point
Copy the full SHA ec23396View commit details -
Django caching instrumentation update (#3009)
This adds more data to the cache spans and makes adding the cache item size optional. This implements parts of following spec https://develop.sentry.dev/sdk/performance/modules/cache/ --------- Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com>
Configuration menu - View commit details
-
Copy full SHA for 30f72a3 - Browse repository at this point
Copy the full SHA 30f72a3View commit details -
Redis Cache Module - 1 - Prepare Code (#3073)
Make the redis integration fit for sending Span data that is eligible for the Caches performance module in Sentry. --------- Co-authored-by: Daniel Szoke <7881302+szokeasaurusrex@users.noreply.github.com> Co-authored-by: Ivana Kellyerova <ivana.kellyerova@sentry.io>
Configuration menu - View commit details
-
Copy full SHA for 121aa0e - Browse repository at this point
Copy the full SHA 121aa0eView commit details -
Configuration menu - View commit details
-
Copy full SHA for 88dd524 - Browse repository at this point
Copy the full SHA 88dd524View commit details -
Configuration menu - View commit details
-
Copy full SHA for fadd277 - Browse repository at this point
Copy the full SHA fadd277View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4e74f91 - Browse repository at this point
Copy the full SHA 4e74f91View commit details -
getsentry-bot committed
May 23, 2024 Configuration menu - View commit details
-
Copy full SHA for 0983f74 - Browse repository at this point
Copy the full SHA 0983f74View commit details -
Do not crash exceptiongroup (by patching excepthook and keeping the n…
…ame of the function) (#3099) By patchinng sys.excepthook and retaining the original name, exceptiongroup is crashing. This is why I changed it to patch exceptgroup and have a new name for the patched function.
Configuration menu - View commit details
-
Copy full SHA for 45bf880 - Browse repository at this point
Copy the full SHA 45bf880View commit details -
Handle also byte arras as strings (#3101)
In some cases it can happen that the array of redis keys to get can be byte arrays and not string. Make sure we can deal with all kinds of keys, no matter if byte array or string.
Configuration menu - View commit details
-
Copy full SHA for 35e9bab - Browse repository at this point
Copy the full SHA 35e9babView commit details -
Configuration menu - View commit details
-
Copy full SHA for f12712f - Browse repository at this point
Copy the full SHA f12712fView commit details -
Configuration menu - View commit details
-
Copy full SHA for a0ea6a9 - Browse repository at this point
Copy the full SHA a0ea6a9View 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 28d890a...a0ea6a9