-
Notifications
You must be signed in to change notification settings - Fork 552
Comparing changes
Open a pull request
base repository: getsentry/sentry-python
base: 1.35.0
head repository: getsentry/sentry-python
compare: 1.36.0
- 10 commits
- 21 files changed
- 6 contributors
Commits on Nov 13, 2023
-
getsentry-bot committed
Nov 13, 2023 Configuration menu - View commit details
-
Copy full SHA for cb7299a - Browse repository at this point
Copy the full SHA cb7299aView commit details
Commits on Nov 14, 2023
-
feat(integrations): Support Django 5.0 (#2490)
Fix the way we wrap signal receivers: Django 5.0 introduced async receivers and changed the signature of the `Signal._live_receivers` method to return both sync and async receivers. We'll need to change the Django version in tox.ini to 5.0 once it's been released. At the moment we're using the 5.0b1 release.
Configuration menu - View commit details
-
Copy full SHA for 44b0244 - Browse repository at this point
Copy the full SHA 44b0244View commit details
Commits on Nov 15, 2023
-
- run test suite with Flask 3.0 - fix `request.get_json()` in the tests (Flask/Werkzeug 3.0 now throws an `UnsupportedMediaType` exception if the `Content-Type` isn't `application/json`)
Configuration menu - View commit details
-
Copy full SHA for 5a6b5d4 - Browse repository at this point
Copy the full SHA 5a6b5d4View commit details
Commits on Nov 16, 2023
-
Do not create a span when task is triggered by Celery Beat (#2510)
We create a span for submitting a Celery task for execution (when apply_async() is called). In cases where web frameworks are calling apply_async() this is fine, because the web framework created a transaction where the span is attached. When Celery Beat wakes up and is calling apply_async() this is not good, because there is no transaction and then the span ID of the newly created span will be given to the task as parent_span_id leading to orphaned transactions. So in case apply_async() is called by Celery Beat, we do not create a span for submitting the task for execution.
Configuration menu - View commit details
-
Copy full SHA for 0c9803a - Browse repository at this point
Copy the full SHA 0c9803aView commit details
Commits on Nov 17, 2023
-
Configuration menu - View commit details
-
Copy full SHA for 9bf6c13 - Browse repository at this point
Copy the full SHA 9bf6c13View commit details
Commits on Nov 18, 2023
-
Ensure
RedisIntegration
is disabled, unlessredis
is installed (#……2504) * Add test to ensure redis integration disabled unless installed * Integrations added to enabled list if actually installed * Move test to test_basics.py * Code review suggestions * Fixed test failures * Add unit test to check multiple `setup_integrations` calls * fix type hint for 2.7 * Added staticmethod * Move test to `test_basics`
Configuration menu - View commit details
-
Copy full SHA for b3ccf96 - Browse repository at this point
Copy the full SHA b3ccf96View commit details
Commits on Nov 20, 2023
-
Fix Quart integration for Quart 0.19.4 (#2516)
* is_coroutine_function was removed from quart, taking from asyncio directly
Configuration menu - View commit details
-
Copy full SHA for 5c17491 - Browse repository at this point
Copy the full SHA 5c17491View commit details -
Handling asgi body in the right way. For real (#2513)
Handling the request body in ASGI applications. By reading the body first it gets cached (by for example Django) which makes it possible to read the body multiple times.
Configuration menu - View commit details
-
Copy full SHA for 91676ec - Browse repository at this point
Copy the full SHA 91676ecView commit details
Commits on Nov 21, 2023
-
Configuration menu - View commit details
-
Copy full SHA for b9d2464 - Browse repository at this point
Copy the full SHA b9d2464View commit details -
Configuration menu - View commit details
-
Copy full SHA for 89ba92a - Browse repository at this point
Copy the full SHA 89ba92aView 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 1.35.0...1.36.0