feat/sync_dec_with_master_v1_6_1

[aarmoa]

• PR to sync dev branch with latest changes in master from the release of v1.6.1

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
pypi/aiohappyeyeballs@2.3.4	network	0	77.4 kB	bdraco
pypi/aiohttp@3.10.1	environment, eval, filesystem, network, shell, unsafe	0	14.3 MB	Andrew.Svetlov, fafhrd, webknjaz
pypi/attrs@24.2.0	environment, eval, filesystem, shell, unsafe	0	1.47 MB	hynek
pypi/cffi@1.17.0	environment, eval, filesystem, network, shell, unsafe	0	2.16 MB	Armin.Rigo, alexgaynor, fijal, ...5 more
pypi/coverage@7.6.1	environment, eval, filesystem, network	0	826 kB	nedbatchelder
pypi/grpcio-tools@1.65.4	environment, eval, filesystem, shell, unsafe	0	27.7 MB	google_opensource, grpc-packages
pypi/grpcio@1.65.4	environment, eval, filesystem, network, shell, unsafe	0	72.2 MB	google_opensource, grpc-packages

🚮 Removed packages:pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/aiohttp@3.9.5, pypi/attrs@23.2.0, pypi/attrs@23.2.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/cffi@1.16.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/coverage@7.6.0, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.65.1, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio-tools@1.66.0rc2, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1, pypi/grpcio@1.65.1

View full report↗︎

[coderabbitai]

Important

Review skipped

More than 25% of the files skipped due to max files limit. The review is being skipped to prevent a low-quality review.

143 files out of 299 files are above the max files limit of 150.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

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.