Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency sentry-sdk to v2.13.0 #2013

Merged
merged 1 commit into from
Aug 13, 2024

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 13, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
sentry-sdk (changelog) ==2.12.0 -> ==2.13.0 age adoption passing confidence

Release Notes

getsentry/sentry-python (sentry-sdk)

v2.13.0

Compare Source

Various fixes & improvements
  • New integration: Ray (#​2400) (#​2444) by @​glowskir

    Usage: (add the RayIntegration to your sentry_sdk.init() call and make sure it is called in the worker processes)

    import ray
    
    import sentry_sdk
    from sentry_sdk.integrations.ray import RayIntegration
    
    def init_sentry():
        sentry_sdk.init(
            dsn="...",
            traces_sample_rate=1.0,
            integrations=[RayIntegration()],
        )
    
    init_sentry()
    
    ray.init(
        runtime_env=dict(worker_process_setup_hook=init_sentry), 
    )

    For more information, see the documentation for the Ray integration.

  • New integration: Litestar (#​2413) (#​3358) by @​KellyWalker

    Usage: (add the LitestarIntegration to your sentry_sdk.init())

    from litestar import Litestar, get
    
    import sentry_sdk
    from sentry_sdk.integrations.litestar import LitestarIntegration
    
    sentry_sdk.init(
        dsn="...",
        traces_sample_rate=1.0,
        integrations=[LitestarIntegration()],
    )
    
    @​get("/")
    async def index() -> str:
        return "Hello, world!"
    
    app = Litestar(...)

    For more information, see the documentation for the Litestar integration.

  • New integration: Dramatiq from @​jacobsvante (#​3397) by @​antonpirker
    Usage: (add the DramatiqIntegration to your sentry_sdk.init())

    import dramatiq
    
    import sentry_sdk
    from sentry_sdk.integrations.dramatiq import DramatiqIntegration
    
    sentry_sdk.init(
        dsn="...",
        traces_sample_rate=1.0,
        integrations=[DramatiqIntegration()],
    )
    
    @​dramatiq.actor(max_retries=0)
    def dummy_actor(x, y):
        return x / y
    
    dummy_actor.send(12, 0)

    For more information, see the documentation for the Dramatiq integration.

  • New config option: Expose custom_repr function that precedes safe_repr invocation in serializer (#​3438) by @​sl0thentr0py

    See: https://docs.sentry.io/platforms/python/configuration/options/#custom-repr

  • Profiling: Add client SDK info to profile chunk (#​3386) by @​Zylphrex

  • Serialize vars early to avoid living references (#​3409) by @​sl0thentr0py

  • Deprecate hub-based sessions.py logic (#​3419) by @​szokeasaurusrex

  • Deprecate is_auto_session_tracking_enabled (#​3428) by @​szokeasaurusrex

  • Add note to generated yaml files (#​3423) by @​sentrivana

  • Slim down PR template (#​3382) by @​sentrivana

  • Use new banner in readme (#​3390) by @​sentrivana


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

  • New Features

    • Updated the Sentry SDK to version 2.13.0, which may include enhancements, new features, and bug fixes related to error tracking and monitoring.
  • Bug Fixes

    • Improvements in error tracking and monitoring capabilities through the upgraded Sentry SDK.

Copy link

coderabbitai bot commented Aug 13, 2024

Caution

Review failed

The pull request is closed.

Walkthrough

Walkthrough

The recent update to the requirements.txt file features an upgrade of the sentry-sdk from version 2.12.0 to 2.13.0. This change enhances the application's error tracking and monitoring capabilities, potentially introducing new features and improvements while maintaining existing functionality.

Changes

File Change Summary
requirements.txt Updated sentry-sdk from 2.12.0 to 2.13.0

Sequence Diagram(s)

(No sequence diagrams needed due to the simplicity of the change.)

Poem

In the fields where the bunnies play,
A new SDK brightens the day! 🌼
Sentry's version now so fine,
Tracking errors, all will shine.
Hop along, the code is neat,
With every change, we feel the beat! 🐇✨


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

deepsource-io bot commented Aug 13, 2024

Here's the code health analysis summary for commits 9c8ec90..4afd438. View details on DeepSource ↗.

Analysis Summary

AnalyzerStatusSummaryLink
DeepSource JavaScript LogoJavaScript✅ SuccessView Check ↗

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

Copy link

sonarcloud bot commented Aug 13, 2024

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The changes regarding library versions seem safe, as long as the minor version update of sentry-sdk has been tested to not cause any breakage. However, the dependencies specified with absolute paths might create problems in different environments.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please ensure that this minor version upgrade of sentry-sdk does not introduce any breaking changes or conflicts with other packages.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
-e file:///home/drazisil/mcos/libs/serializable#egg=serializable
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method of specifying dependencies can lead to problems when the code is deployed to a different machine or environment. It would be better to include 'serializable' in the requirements file with a specified version, if possible.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
-e file:///home/drazisil/mcos/libs/serializable#egg=serializable
-e file:///home/drazisil/mcos/projects/server#egg=server
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As with the previous comment, this could lead to deployment issues across different machines or environments. If 'server' can be included in the requirements file with a specific version, that would likely be a better approach.

Copy link

@codecov codecov bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The code mainly updates the version of sentry-sdk library from 2.12.0 to 2.13.0. It is important to ensure that this version change does not break existing functionality or requires code changes. Additionally, the use of local file paths for serializable and server dependencies might cause issues in terms of portability and needs to be addressed.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We are upgrading sentry-sdk from version 2.12.0 to 2.13.0. Make sure to test if the new version is compatible with the rest of the code, to ensure it doesn't break anything.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
-e file:///home/drazisil/mcos/libs/serializable#egg=serializable
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This project appears to use a local dependency for serializable package. This may cause issues in terms of portability. Consider upload the library to a private package index or include the library code in the project itself if possible.

@@ -25,7 +25,7 @@ pycodestyle==2.12.1
pyflakes==3.2.0
pytest==8.3.2
pyyaml==6.0.2
sentry-sdk==2.12.0
sentry-sdk==2.13.0
-e file:///home/drazisil/mcos/libs/serializable#egg=serializable
-e file:///home/drazisil/mcos/projects/server#egg=server
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Similarly, the local path of server package may cause portability concerns, especially if this code is to be run across different environments. Consider making the library more accessible, maybe by hosting it on a common, accessible server or including it into the project itself.

@renovate renovate bot added this pull request to the merge queue Aug 13, 2024
Copy link

codecov bot commented Aug 13, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 10.51%. Comparing base (9c8ec90) to head (4afd438).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2013   +/-   ##
=======================================
  Coverage   10.51%   10.51%           
=======================================
  Files          97       97           
  Lines        8503     8503           
  Branches      106      106           
=======================================
  Hits          894      894           
  Misses       7609     7609           
Flag Coverage Δ *Carryforward flag
cli 0.00% <ø> (ø) Carriedforward from 9c8ec90
connection 25.26% <ø> (ø) Carriedforward from 9c8ec90
database 9.15% <ø> (ø) Carriedforward from 9c8ec90
gateway 41.37% <ø> (ø) Carriedforward from 9c8ec90
mcots 0.00% <ø> (ø) Carriedforward from 9c8ec90
nps 0.00% <ø> (ø) Carriedforward from 9c8ec90
patch 86.08% <ø> (ø) Carriedforward from 9c8ec90
shard 41.47% <ø> (ø) Carriedforward from 9c8ec90
shared 13.44% <ø> (ø) Carriedforward from 9c8ec90
shared-packets 0.00% <ø> (ø) Carriedforward from 9c8ec90

*This pull request uses carry forward flags. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Merged via the queue into main with commit dd30ceb Aug 13, 2024
9 checks passed
@renovate renovate bot deleted the renovate/sentry-sdk-2.x branch August 13, 2024 17:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants