Hello community, here is the log from the commit of package python-sentry-sdk for openSUSE:Factory checked in at 2019-08-22 10:58:15 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Comparing /work/SRC/openSUSE:Factory/python-sentry-sdk (Old) and /work/SRC/openSUSE:Factory/.python-sentry-sdk.new.22127 (New) ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Package is "python-sentry-sdk" Thu Aug 22 10:58:15 2019 rev:3 rq:725152 version:0.11.1 Changes: -------- --- /work/SRC/openSUSE:Factory/python-sentry-sdk/python-sentry-sdk.changes 2019-08-19 21:39:05.192320506 +0200 +++ /work/SRC/openSUSE:Factory/.python-sentry-sdk.new.22127/python-sentry-sdk.changes 2019-08-22 10:58:19.501651955 +0200 @@ -1,0 +2,7 @@ +Mon Aug 19 20:18:33 UTC 2019 - Jimmy Berry <[email protected]> + +- Update to 0.11.1 + - Remove a faulty assertion (observed in environment with + Django Channels and ASGI). + +------------------------------------------------------------------- Old: ---- python-sentry-sdk-0.11.0.tar.gz New: ---- python-sentry-sdk-0.11.1.tar.gz ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Other differences: ------------------ ++++++ python-sentry-sdk.spec ++++++ --- /var/tmp/diff_new_pack.blwYCS/_old 2019-08-22 10:58:20.633651803 +0200 +++ /var/tmp/diff_new_pack.blwYCS/_new 2019-08-22 10:58:20.637651803 +0200 @@ -18,7 +18,7 @@ %{?!python_module:%define python_module() python-%{**} python3-%{**}} Name: python-sentry-sdk -Version: 0.11.0 +Version: 0.11.1 Release: 0 Summary: Python SDK for Sentry.io License: BSD-2-Clause ++++++ python-sentry-sdk-0.11.0.tar.gz -> python-sentry-sdk-0.11.1.tar.gz ++++++ diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/CHANGES.md new/sentry-python-0.11.1/CHANGES.md --- old/sentry-python-0.11.0/CHANGES.md 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/CHANGES.md 2019-08-19 12:46:07.000000000 +0200 @@ -27,6 +27,10 @@ A major release `N` implies the previous release `N-1` will no longer receive updates. We generally do not backport bugfixes to older versions unless they are security relevant. However, feel free to ask for backports of specific commits on the bugtracker. +## 0.11.1 + +* Remove a faulty assertion (observed in environment with Django Channels and ASGI). + ## 0.11.0 * Fix type hints for the logging integration. Thansk Steven Dignam! diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/CONTRIBUTING.md new/sentry-python-0.11.1/CONTRIBUTING.md --- old/sentry-python-0.11.0/CONTRIBUTING.md 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/CONTRIBUTING.md 2019-08-19 12:46:07.000000000 +0200 @@ -20,6 +20,35 @@ The usual release process goes like this: -1. Go through git log and write new entry into `CHANGELOG.md`, commit to master +1. Go through git log and write new entry into `CHANGES.md`, commit to master 2. `craft p a.b.c` 3. `craft pp a.b.c` + +## Adding a new integration (checklist) + +1. Write the integration. + + * Instrument all application instances by default. Prefer global signals/patches instead of configuring a specific instance. Don't make the user pass anything to your integration for anything to work. Aim for zero configuration. + + * Everybody monkeypatches. That means: + + * Make sure to think about conflicts with other monkeypatches when monkeypatching. + + * You don't need to feel bad about it. + + * Avoid modifying the hub, registering a new client or the like. The user drives the client, and the client owns integrations. + + * Allow the user to disable the integration by changing the client. Check `Hub.current.get_integration(MyIntegration)` from within your signal handlers to see if your integration is still active before you do anything impactful (such as sending an event). + +2. Write the [docs](https://github.com/getsentry/sentry-docs). Answer the following questions: + + * What does your integration do? Split in two sections: Executive summary at top and exact behavior further down. + + * Which version of the SDK supports which versions of the modules it hooks into? + + * One code example with basic setup. + + Tip: Put most relevant parts wrapped in `<!--WIZARD-->..<!--ENDWIZARD-->` tags for usage from within the Sentry UI. + +3. Merge docs after new version has been released (auto-deploys on merge). +4. (optional) Update data in [`sdk_updates.py`](https://github.com/getsentry/sentry/blob/master/src/sentry/sdk_updates.py) to give users in-app suggestions to use your integration. May not be applicable or doable for all kinds of integrations. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/docs/conf.py new/sentry-python-0.11.1/docs/conf.py --- old/sentry-python-0.11.0/docs/conf.py 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/docs/conf.py 2019-08-19 12:46:07.000000000 +0200 @@ -22,7 +22,7 @@ copyright = u"2019, Sentry Team and Contributors" author = u"Sentry Team and Contributors" -release = "0.11.0" +release = "0.11.1" version = ".".join(release.split(".")[:2]) # The short X.Y version. diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/sentry_sdk/consts.py new/sentry-python-0.11.1/sentry_sdk/consts.py --- old/sentry-python-0.11.0/sentry_sdk/consts.py 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/sentry_sdk/consts.py 2019-08-19 12:46:07.000000000 +0200 @@ -71,7 +71,7 @@ del _get_default_options -VERSION = "0.11.0" +VERSION = "0.11.1" SDK_INFO = { "name": "sentry.python", "version": VERSION, diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/sentry_sdk/tracing.py new/sentry-python-0.11.1/sentry_sdk/tracing.py --- old/sentry-python-0.11.0/sentry_sdk/tracing.py 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/sentry_sdk/tracing.py 2019-08-19 12:46:07.000000000 +0200 @@ -5,7 +5,7 @@ from datetime import datetime import sentry_sdk -from sentry_sdk.utils import capture_internal_exceptions +from sentry_sdk.utils import capture_internal_exceptions, logger from sentry_sdk._compat import PY2 from sentry_sdk._types import MYPY @@ -272,9 +272,9 @@ # resolved to a concrete decision. If `sampled` is `None`, it's # likely that somebody used `with sentry_sdk.Hub.start_span(..)` on a # non-transaction span and later decided to make it a transaction. - assert ( - self.sampled is not None - ), "Need to set transaction when entering span!" + if self.sampled is None: + logger.warning("Discarding transaction Span without sampling decision") + return None return hub.capture_event( diff -urN '--exclude=CVS' '--exclude=.cvsignore' '--exclude=.svn' '--exclude=.svnignore' old/sentry-python-0.11.0/setup.py new/sentry-python-0.11.1/setup.py --- old/sentry-python-0.11.0/setup.py 2019-08-16 15:05:56.000000000 +0200 +++ new/sentry-python-0.11.1/setup.py 2019-08-19 12:46:07.000000000 +0200 @@ -12,7 +12,7 @@ setup( name="sentry-sdk", - version="0.11.0", + version="0.11.1", author="Sentry Team and Contributors", author_email="[email protected]", url="https://github.com/getsentry/sentry-python";,
