Skip to content

Update Rust crate oxide-tokio-rt to 0.1.4#244

Open
oxide-renovate[bot] wants to merge 1 commit intomainfrom
renovate/oxide-tokio-rt-0.x
Open

Update Rust crate oxide-tokio-rt to 0.1.4#244
oxide-renovate[bot] wants to merge 1 commit intomainfrom
renovate/oxide-tokio-rt-0.x

Conversation

@oxide-renovate
Copy link
Copy Markdown

@oxide-renovate oxide-renovate bot commented Apr 1, 2026

This PR contains the following updates:

Package Type Update Change
oxide-tokio-rt workspace.dependencies patch 0.1.20.1.4

Release Notes

oxidecomputer/oxide-tokio-rt (oxide-tokio-rt)

v0.1.4

Compare Source

Summary

This updates our minimum Tokio version to 1.52.0. This allows us to
pick up two major fixes that will change our default runtime
configuration:

  • Tokio PR tokio-rs/tokio#7431, released in 1.51.0, changes the
    multi-threaded runtime to allow tasks in the LIFO slot to participate in
    work-stealing. Therefore, it should no longer be necessary to disable
    the LIFO slot optimization, as the pathology where a task placed in the
    LIFO slot can become permanently or semi-permanently stuck while the
    task that notified them runs for a long time without yielding can no
    longer occur.

  • Tokio PR tokio-rs/tokio#8010, released in 1.52.0,
    which adds eager handoff for the I/O and time drivers in the multi-threaded
    runtime. This is currently an experimental feature, although it is your
    author's opinion that this is really a fix for incorrect runtime behavior. It
    changes worker threads in the multi-threaded runtime to wake another
    worker prior to polling tasks if that worker had previously been parked
    on the I/O driver or timer wheel. Eagerly handing off these resources
    should prevent pathologies such as omicron#9619.

After updating Tokio, PR #​7 changed the default runtime settings to
stop disabling the LIFO slot optimization, and enable eager driver
hand-off.

What's Changed

New Contributors

Full Changelog: oxidecomputer/oxide-tokio-rt@v0.1.3...v0.1.4

v0.1.3

Compare Source

Summary

This release adds an OxideBuilder for configuring oxide-tokio-rt-specific settings.

What's Changed

Full Changelog: oxidecomputer/oxide-tokio-rt@v0.1.2...v0.1.3


Configuration

📅 Schedule: (in timezone America/Los_Angeles)

  • Branch creation
    • "after 8pm,before 6am"
  • Automerge
    • "after 8pm,before 6am"

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 has been generated by Renovate Bot.

@oxide-renovate oxide-renovate bot added the dependencies Pull requests that update a dependency file label Apr 1, 2026
@oxide-renovate oxide-renovate bot force-pushed the renovate/oxide-tokio-rt-0.x branch from d3e67d2 to 7c9140b Compare April 16, 2026 03:59
@oxide-renovate oxide-renovate bot changed the title Update Rust crate oxide-tokio-rt to 0.1.3 Update Rust crate oxide-tokio-rt to 0.1.4 Apr 16, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants