Bump mio from 0.8.5 to 0.8.11

[dependabot]

Bumps mio from 0.8.5 to 0.8.11.

Changelog

Sourced from mio's changelog.

0.8.11

• Fix receiving IOCP events after deregistering a Windows named pipe (tokio-rs/mio#1760, backport pr: tokio-rs/mio#1761).

0.8.10

Added

• Solaris support (tokio-rs/mio#1724).

0.8.9

Added

• ESP-IDF framework support (tokio-rs/mio#1692).
• AIX operating system support (tokio-rs/mio#1704).
• Vita support (tokio-rs/mio#1721).
• {UnixListener,UnixStream}:bind_addr (tokio-rs/mio#1630).
• mio_unsupported_force_poll_poll and mio_unsupported_force_waker_pipe unsupported configuration flags to force a specific poll or waker implementation (tokio-rs/mio#1684, tokio-rs/mio#1685, tokio-rs/mio#1692).

Fixed

• The pipe(2) based waker (swapped file descriptors) (tokio-rs/mio#1722).
• The duplicate waker check to work correctly with cloned Registrys. (tokio-rs/mio#1706).

0.8.8

Fixed

• Fix compilation on WASI (tokio-rs/mio#1676).

0.8.7

Added

• Add/fix support for tvOS and watchOS, Mio should now build for tvOS and

... (truncated)

Commits

• 0328bde Release v0.8.11
• 7084498 Fix warnings
• 90d4fe0 named-pipes: fix receiving IOCP events after deregister
• c710a30 Add v0.8.x to the CI
• c29e21c Release v0.8.10
• f6a20da Add Solaris operating system support (#1724)
• e80c3b2 Release v0.8.9
• 862786b Fix importing of IoSourceState
• 4034872 Add support for vita target
• 8eb4010 Fix receiver and sender fd in pipe based waker
• 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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[juntao]

Hello, I am a code review bot on flows.network. Here are my reviews of code commits in this PR.

---

Commit 68670a8fa31a3f443985b921bf745c3b771afa25

Key Changes:

• The patch updates the mio dependency from version 0.8.5 to version 0.8.11.
• It also updates the libc dependency from version 0.2.139 to version 0.2.153.

Potential Problems:

1. Compatibility with Other Dependencies: The update to mio and libc versions may introduce compatibility issues with other dependencies that rely on specific versions of these crates. It's essential to ensure that all dependencies still work correctly with the updated versions.

2. Functionality Changes: The update from 0.8.5 to 0.8.11 in the mio crate could include functionality changes or deprecations that might require code adjustments in the project using this dependency.

3. Security Concerns: While the patch does not mention any security fixes, it's crucial to review the release notes and changelog of both mio and libc to check for any security patches or vulnerabilities that might have been addressed in the newer versions.

4. Build and Runtime Errors: The update can potentially lead to build or runtime errors if the API changes in the newer versions of the dependencies are not handled properly in the existing codebase.

As a reviewer, it's recommended to test the changes thoroughly, review the impact on the project, and consider any necessary modifications to ensure a smooth transition to the updated dependencies.