Releases: getsentry/sentry-python
Releases · getsentry/sentry-python
0.12.3
- Various performance improvements to event sending.
- Avoid crashes when scope or hub is racy.
- Revert a change that broke applications using gevent and channels (in the same virtualenv, but different processes).
- Fix a bug that made the SDK crash on unicode in SQL.
0.12.2
0.12.1
0.12.0
- Sentry now has a Discord server! Join the server to get involved into SDK development and ask questions.
- Fix a bug where the response object for httplib (or requests) was held onto for an unnecessarily long amount of time.
- APM: Add spans for more methods on
subprocess.Popen
objects. - APM: Add spans for Django middlewares.
- APM: Add spans for ASGI requests.
- Automatically inject the ASGI middleware for Django Channels 2.0. This will break your Channels 2.0 application if it is running on Python 3.5 or 3.6 (while previously it would "only" leak a lot of memory for each ASGI request). Install
aiocontextvars
from PyPI to make it work again.
0.11.2
0.11.1
0.11.0
- Fix type hints for the logging integration. Thansk Steven Dignam!
- Fix an issue where scope/context data would leak in applications that use
gevent
with its threading monkeypatch. The fix is to avoid usage of contextvars in such environments. Thanks Ran Benita! - Fix a reference cycle in the
ThreadingIntegration
that led to exceptions on interpreter shutdown. Thanks Guang Tian Li! - Fix a series of bugs in the stdlib integration that broke usage of
subprocess
. - More instrumentation for APM.
- New integration for SQLAlchemy (creates breadcrumbs from queries).
- New (experimental) integration for Apache Beam.
- Fix a bug in the
LoggingIntegration
that would send breadcrumbs timestamps in the wrong timezone. - The
AiohttpIntegration
now sets the event's transaction name. - Fix a bug that caused infinite recursion when serializing local variables that logged errors or otherwise created Sentry events.
0.10.2
- Fix a bug where a log record with non-strings as
extra
keys would make the SDK crash. - Added ASGI integration for better hub propagation, request data for your events and capturing uncaught exceptions. Using this middleware explicitly in your code will also fix a few issues with Django Channels.
- Fix a bug where
celery-once
was deadlocking when used in combination with the celery integration. - Fix a memory leak in the new tracing feature when it is not enabled.
0.10.1
0.10.0
- Massive refactor in preparation to tracing. There are no intentional breaking
changes, but there is a risk of breakage (hence the minor version bump). Two
new client optionstraces_sample_rate
andtraceparent_v2
have been added.
Do not change the defaults in production, they will bring your application
down or at least fill your Sentry project up with nonsense events.