Update Rust crate oxide-tokio-rt to 0.1.5

[oxide-renovate]

This PR contains the following updates:

Package	Type	Update	Change
oxide-tokio-rt	workspace.dependencies	patch	0.1.2 → 0.1.5

---

Release Notes

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

v0.1.5

Compare Source

What's Changed

• fix: re-enable disabling the LIFO slot by @​hawkw in #​11
• chore: prepare to release v0.1.5 by @​hawkw in #​12

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

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

• Add better error message if someone has a global Cargo config by @​emilyalbini in #​5
• fix weird line break by @​iximeow in #​8
• tokio 1.52.0 and related changes by @​hawkw in #​7
• chore: prepare to release v0.1.4 by @​hawkw in #​9

New Contributors

• @​emilyalbini made their first contribution in #​5
• @​iximeow made their first contribution in #​8

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

• feat: Add dedicated signal-handling thread by @​hawkw in #​4

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 Mend Renovate.

[oxide-renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.