Remove nix from the public API #549
Annotations
10 errors and 8 warnings
|
Run tests with signals:
tests/signals.rs#L43
no variant or associated item named `SIGUSR1` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L45
no variant or associated item named `SIGUSR1` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L52
no variant or associated item named `SIGUSR1` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L66
no variant or associated item named `SIGUSR1` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L78
no variant or associated item named `SIGUSR2` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L82
no variant or associated item named `SIGUSR2` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L88
no variant or associated item named `SIGUSR2` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L96
no variant or associated item named `SIGUSR1` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L96
no variant or associated item named `SIGUSR2` found for enum `calloop::signals::Signal` in the current scope
|
|
Run tests with signals:
tests/signals.rs#L108
no variant or associated item named `SIGUSR2` found for enum `calloop::signals::Signal` in the current scope
|
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions-rs/toolchain@v1, actions-rs/cargo@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-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/
|
|
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 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/
|
|
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/
|
Loading