Bump tokio from 1.38.0 to 1.41.1

[dependabot]

Bumps tokio from 1.38.0 to 1.41.1.

Release notes

Sourced from tokio's releases.

Tokio v1.41.1

1.41.1 (Nov 7th, 2024)

Fixed

• metrics: fix bug with wrong number of buckets for the histogram (#6957)
• net: display net requirement for net::UdpSocket in docs (#6938)
• net: fix typo in TcpStream internal comment (#6944)

#6957: tokio-rs/tokio#6957 #6938: tokio-rs/tokio#6938 #6944: tokio-rs/tokio#6944

Tokio v1.41.0

1.41.0 (Oct 22th, 2024)

Added

• metrics: stabilize global_queue_depth (#6854, #6918)
• net: add conversions for unix SocketAddr (#6868)
• sync: add watch::Sender::sender_count (#6836)
• sync: add mpsc::Receiver::blocking_recv_many (#6867)
• task: stabilize Id apis (#6793, #6891)

Added (unstable)

• metrics: add H2 Histogram option to improve histogram granularity (#6897)
• metrics: rename some histogram apis (#6924)
• runtime: add LocalRuntime (#6808)

Changed

• runtime: box futures larger than 16k on release mode (#6826)
• sync: add #[must_use] to Notified (#6828)
• sync: make watch cooperative (#6846)
• sync: make broadcast::Receiver cooperative (#6870)
• task: add task size to tracing instrumentation (#6881)
• wasm: enable cfg_fs for wasi target (#6822)

Fixed

• net: fix regression of abstract socket path in unix socket (#6838)

Documented

• io: recommend OwnedFd with AsyncFd (#6821)
• io: document cancel safety of AsyncFd methods (#6890)
• macros: render more comprehensible documentation for join and try_join (#6814, #6841)
• net: fix swapped examples for TcpSocket::set_nodelay and TcpSocket::nodelay (#6840)
• sync: document runtime compatibility (#6833)

... (truncated)

Commits

• bb7ca75 chore: prepare Tokio v1.41.1 (#6959)
• 4a34b77 metrics: fix bug with wrong number of buckets for the histogram (#6957)
• 8897885 docs: fix mismatched backticks in CONTRIBUTING.md (#6951)
• 0dbdd19 ci: update cargo-check-external-types to 0.1.13 (#6949)
• 94e55c0 net: fix typo in TcpStream internal comment (#6944)
• 4468f27 metrics: fixed flaky worker_steal_count test (#6932)
• 070a825 metrics: removed race condition from global_queue_depth_multi_thread test (#6...
• 946401c net: display net requirement for net::UdpSocket in docs (#6938)
• 0c01fd2 ci: use patched version of cargo-check-external-types to fix CI failure (#6937)
• ebe2416 ci: use cargo deny (#6931)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.

[dryrunsecurity]

DryRun Security Summary

The pull request updates the mio and tokio dependencies to newer versions, which requires careful review to ensure there are no security vulnerabilities or breaking changes that could impact the application's functionality or security.

Expand for full summary

Summary:

The code changes in this pull request focus on updating the mio and tokio dependencies to newer versions. The mio dependency is being updated from version 0.8.11 to 1.0.2, which is a major version update and could potentially introduce breaking changes. The tokio dependency is being updated from version 1.38.0 to 1.41.1, which is a minor version update and is less likely to have breaking changes. Additionally, the tokio-macros dependency is being updated from version 2.3.0 to 2.4.0.

From an application security perspective, it's important to carefully review the changes in the newer versions of these dependencies to ensure that there are no new security vulnerabilities or breaking changes that could impact the application's functionality or security. It's also a good idea to thoroughly test the application after the dependency updates to ensure that everything is working as expected.

Files Changed:

• Cargo.lock: This file contains the exact versions of dependencies used by the application. The changes update the mio, tokio, and tokio-macros dependencies to newer versions.

Code Analysis

We ran 9 analyzers against 1 file and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.