Bump thiserror from 1.0.64 to 1.0.65 #5857
Annotations
2 errors and 26 warnings
|
Run tests under wasm32-wasi
Rayon cannot be used when targeting wasi32. Try disabling default features.
|
|
Run tests under wasm32-wasi
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
The following actions use a deprecated Node.js version and will be forced to run on node20: actions-rs/toolchain@v1, actions-rs/cargo@v1. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
|
|
Install wasm32-wasi target
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Install wasm32-wasi target
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Install wasm32-wasi target
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Install wasm32-wasi target
The `set-output` command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
|
|
Build code with cargo-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
Build code with cargo-wasi
`cfg-if` (lib) generated 1 warning
|
|
Build code with cargo-wasi
`wasi` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`libm` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`num-traits` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`ppv-lite86` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`memchr` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`bytemuck` (lib) generated 1 warning (1 duplicate)
|
|
Build code with cargo-wasi
`num-integer` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
the `wasm32-wasi` target is being renamed to `wasm32-wasip1` and the `wasm32-wasi` target will be removed from nightly in October 2024 and removed from stable Rust in January 2025
|
|
Run tests under wasm32-wasi
`cfg-if` (lib) generated 1 warning
|
|
Run tests under wasm32-wasi
`libc` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`lazy_static` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`memchr` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`libm` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`wasi` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`getrandom` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`rand_core` (lib) generated 1 warning (1 duplicate)
|
|
Run tests under wasm32-wasi
`ppv-lite86` (lib) generated 1 warning (1 duplicate)
|
Loading