Skip to content

Update to use RandomAccess that returns owned futures #17

Update to use RandomAccess that returns owned futures

Update to use RandomAccess that returns owned futures #17

Triggered via pull request March 17, 2026 20:18
@cowlickscowlicks
synchronize #52
owned-futures
Status Failure
Total duration 52s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 5 warnings
test-linux
Process completed with exit code 101.
test-macos
Process completed with exit code 101.
build-extra
Process completed with exit code 101.
type annotations needed: src/lib.rs#L337
error[E0282]: type annotations needed --> src/lib.rs:337:13 | 337 | let mut file = OpenOptions::new() | ^^^^^^^^ ... 344 | file.sync_all().await?; | ---- type must be known at this point | help: consider giving `file` an explicit type | 337 | let mut file: /* Type */ = OpenOptions::new() | ++++++++++++
type annotations needed: src/unix.rs#L7
error[E0282]: type annotations needed --> src/unix.rs:7:9 | 7 | let meta = file.metadata().await?; | ^^^^ 8 | let block_size = meta.blksize(); | ---- type must be known at this point | help: consider giving `meta` an explicit type | 7 | let meta: /* Type */ = file.metadata().await?; | ++++++++++++
unresolved import `tokio`: src/unix.rs#L2
error[E0432]: unresolved import `tokio` --> src/unix.rs:2:5 | 2 | use tokio::fs; | ^^^^^ use of unresolved module or unlinked crate `tokio` | = help: if you wanted to use a crate named `tokio`, use `cargo add tokio` to add it to your `Cargo.toml`
unresolved import `tokio`: src/lib.rs#L96
error[E0432]: unresolved import `tokio` --> src/lib.rs:96:5 | 96 | use tokio::{ | ^^^^^ use of unresolved module or unlinked crate `tokio` | = help: if you wanted to use a crate named `tokio`, use `cargo add tokio` to add it to your `Cargo.toml`
failed to resolve: use of unresolved module or unlinked crate `tokio`: src/lib.rs#L96
error[E0433]: failed to resolve: use of unresolved module or unlinked crate `tokio` --> src/lib.rs:96:5 | 96 | use tokio::{ | ^^^^^ use of unresolved module or unlinked crate `tokio` | = help: if you wanted to use a crate named `tokio`, use `cargo add tokio` to add it to your `Cargo.toml`
lint
Clippy had exited with the 101 exit code
test-windows
Process completed with exit code 1.
test-linux
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test-macos
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
build-extra
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
lint
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions-rs/clippy-check@v1, actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
test-windows
Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@v3. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/