Next Python SDK major - #5005
Draft
sentrivana wants to merge 290 commits into
Draft
sentrivana wants to merge 290 commits into
sentrivana wants to merge 290 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #5005 +/- ##
===========================================
+ Coverage 70.55% 83.76% +13.21%
===========================================
Files 180 180
Lines 18077 18080 +3
Branches 3008 3009 +1
===========================================
+ Hits 12754 15145 +2391
+ Misses 4432 1943 -2489
- Partials 891 992 +101
|
Closed
Contributor
Codecov Results 📊✅ 62922 passed | ❌ 2 failed | ⏭️ 2890 skipped | Total: 65814 | Pass Rate: 95.61% | Execution Time: 178m 51s 📊 Comparison with Base Branch
➕ New Tests (1)View new tests
❌ Failed Tests
|
Contributor
Semver Impact of This PR⚪ None (no version bump detected) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛Anthropic
Documentation 📚
Internal Changes 🔧
Other
🤖 This preview updates automatically when you update the PR. |
![sentry-warden[bot]](https://avatars.githubusercontent.com/in/2755838?s=60&v=4){kind=small}
Fixes for things that the bots [surfaced](#5005) on the major branch: - some version checks were too late (after patching) - fix TrytondWSGI integration name/`_MIN_VERSIONS` entry mismatch Also, changed the warning of the `DidNotEnable` message from "X not installed" to "X not installed or incompatible".
Strawberry is not auto-enabling in 3.0 anymore, so this guard is not necessary.
### Description Remove the `@ai_track` decorator and associated tests #### Issues Part of #6894
### Description The actual compat code was removed with the contextvars shim. Just test utils remain. #### Issues Closes #4997
Drop support for redis-py<[4.2](https://pypi.org/project/redis/4.2.0/): - remove redis cluster legacy (it was moved directly into redis-py in 4.1) - remove deprecated `max_data_size` integration option - remove conditional patching of async client and pipeline -- just patch always (they're available from 4.2+) - use the Redis class instead of StrictRedis (which is just an alias)
There's a `data_collection` version of the removed tests. Closes https://linear.app/getsentry/issue/PY-2810/remove-send-default-pii-from-ariadne
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
### Description
- drop `send_default_pii` support from aws-lambda integration.
- explicitly use `data_collection: {}` in `sentry_init(...)` to fallback
to default config.
#### Issues
Resolves #7585
Also added some empty lines to tests to make them easier to parse Closes https://linear.app/getsentry/issue/PY-2811/remove-send-default-pii-from-celery
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
The parameter allowed users to opt out of collecting GenAI attributes while keeping `send_default_pii=True`. It is ignored when data collection is used, and the major release drops `send_default_pii` in favor of data collection.
…ent spans (#7521) Remove the response streaming flag from Invoke Agent spans because it is ambiguous for an agent that makes multiple model calls in the course of its execution. Each model call may be synchronous or streamed, independently.
There is no need for agents to be under a common parent in span-first, since agents that hand off to each other share the same trace ID in the streaming trace lifecycle (sibling agent invocation spans).
### Description - remove `send_default_pii` branching in `tests_s3.py`. - Remove `send_default_pii` fallback from `tracing_utils.get_url_attributes()` #### Issues Resolves #7658
### Description - remove `send_default_pii` parametrization cases from `DATA_COLLECTION_USER_INFO_CASES`. - update comments.
Port of #4164 See #3913 for an example of an exception chain that is currently not working properly. Closes https://linear.app/getsentry/issue/PY-1948/better-handling-of-exception-groups --------- Co-authored-by: Claude Opus 4.6 <noreply@anthropic.com>
If `before_breadcrumb`, an event processor, or an error processor raises an exception, the associated breadcrumb or event should be discarded as per spec. Change goes into new major since it's breaking.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
8 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
We're preparing our next major on this branch.
The project is tracked in Linear. If you don't have access, we'll try to tag issues belonging to the project with the
SDK3.0 label on GitHub so that you can follow along.Notable changes
Context
You might have read this announcement about us discontinuing work on a 3.0. This is referring to the work done on the
potel-basebranch, which included two types of changes: a huge refactor of our tracing code on the one hand, and various unrelated changes, improvements and fixes on the other. We're dropping the huge refactor part, and only porting the rest, to a new branch and eventually a new 3.0 release.