wayland-client: Add tokio feature for AsyncEventQueue #1130
Annotations
9 errors and 12 warnings
|
Clippy
could not compile `wayland-client` (lib) due to 7 previous errors
|
|
Clippy
Unable to create clippy annotations! Reason: HttpError: Resource not accessible by integration
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L49
redundant field names in struct initialization
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L76
this `else { if .. }` block can be collapsed
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L116
manual implementation of an assign operation
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L128
an implementation of `From` is preferred since it gives you `Into<_>` for free where the reverse isn't true
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L175
the following explicit lifetimes could be elided: 'a
|
|
Clippy:
wayland-client/src/async_event_queue.rs#L180
the following explicit lifetimes could be elided: 'a
|
|
Clippy
Exiting due to clippy errors
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1, actions-rs/clippy-check@v1. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
|
|
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/checkout@v2, actions/cache@v2, actions-rs/toolchain@v1, actions-rs/cargo@v1, actions-rs/clippy-check@v1. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
|
|
Clippy
[email protected]: Compiler version doesn't include clang or GCC: "cc" "--version"
|
|
Clippy
It seems that this Action is executed from the forked repository.
|
|
Clippy
GitHub Actions are not allowed to create Check annotations, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.
|
|
Rust toolchain
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/
|
|
Rust toolchain
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/
|
|
Rust toolchain
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/
|
|
Rust toolchain
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/
|
|
Get date for registry cache
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/
|
|
Get cargo-cache latest version
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/
|
|
Get rustc version for caching
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/
|
Loading