-
Notifications
You must be signed in to change notification settings - Fork 552
Comparing changes
Open a pull request
base repository: getsentry/sentry-python
base: 2.31.0
head repository: getsentry/sentry-python
compare: 2.32.0
- 11 commits
- 17 files changed
- 9 contributors
Commits on Jun 24, 2025
-
feat(sessions): Add top-level start- and end session methods (#4474)
Closes #4473. Co-authored-by: Cursor Agent <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 8b6e5ad - Browse repository at this point
Copy the full SHA 8b6e5adView commit details -
getsentry-bot committed
Jun 24, 2025 Configuration menu - View commit details
-
Copy full SHA for 65d31af - Browse repository at this point
Copy the full SHA 65d31afView commit details
Commits on Jun 25, 2025
-
fix(Litestar): Apply
failed_request_status_codes
to exceptions rais……ed in middleware (#4074) This is a fix for #4021: exceptions raised in middleware were sent without taking into account `failed_request_status_codes` value. See the test case for an example. --------- Co-authored-by: Anton Pirker <[email protected]> Co-authored-by: Daniel Szoke <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for dae0218 - Browse repository at this point
Copy the full SHA dae0218View commit details -
fix(langchain): Ensure no duplicate
SentryLangchainCallback
(#4485)Ensure that `SentryLangchainCallback` does not get added twice by also checking the `inheritable_callbacks` Fixes #4443
Configuration menu - View commit details
-
Copy full SHA for 0a2d858 - Browse repository at this point
Copy the full SHA 0a2d858View commit details -
fix(langchain): Make
span_map
an instance variable (#4476)`span_map` should be an instance variable; otherwise, separate instances of the `SentryLangchainCallback` share the same `span_map` object, which is clearly not intended here. Also, remove the `max_span_map_size` class variable, it is always set on the instance, and so not needed. Ref #4443 Co-authored-by: Cursor Agent <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 7804260 - Browse repository at this point
Copy the full SHA 7804260View commit details -
fix(integrations/ray): Correctly pass keyword arguments to ray.remote…
… function (#4430) Monkey-patched implementation was passing the provided keyword arguments incorrectly due to a typo - "*kwargs" was used instead of "**kwargs" twice. Fixed integration started hitting an assert in the Ray codebase that requires for users to use "@ray.remote" decorator either with no arguments and no parentheses, or with some of the arguments provided. An additional wrapper function was added to support both scenarios. --------- Co-authored-by: Ivana Kellyer <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for ab2e3f0 - Browse repository at this point
Copy the full SHA ab2e3f0View commit details
Commits on Jun 26, 2025
-
Set tool span to failed if an error is raised in the tool (#4527)
Co-authored-by: Ivana Kellyer <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for 546ce1f - Browse repository at this point
Copy the full SHA 546ce1fView commit details -
Configuration menu - View commit details
-
Copy full SHA for bca8816 - Browse repository at this point
Copy the full SHA bca8816View commit details -
Configuration menu - View commit details
-
Copy full SHA for c815a32 - Browse repository at this point
Copy the full SHA c815a32View commit details
Commits on Jun 27, 2025
-
zope.event [released](https://pypi.org/project/zope.event/#history) a new version recently that broke our gevent ci
Configuration menu - View commit details
-
Copy full SHA for 2634a52 - Browse repository at this point
Copy the full SHA 2634a52View commit details -
Configuration menu - View commit details
-
Copy full SHA for 4b022dc - Browse repository at this point
Copy the full SHA 4b022dcView 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 2.31.0...2.32.0