feat: use nwaku instead of go-waku #259
Annotations
3 errors and 13 warnings
Run actions-rs/cargo@v1:
waku-bindings/src/lib.rs#L11
unresolved imports `node::Event`, `node::Signal`, `node::WakuMessageEvent`
|
Run actions-rs/cargo@v1:
waku-bindings/src/utils.rs#L37
mismatched types
|
Run actions-rs/cargo@v1
The process '/home/runner/.cargo/bin/cargo' failed with exit code 101
|
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/checkout@v3, actions/setup-go@v3, 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/
|
Run actions-rs/toolchain@v1
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/
|
Run actions-rs/toolchain@v1
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/
|
Run actions-rs/toolchain@v1
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/
|
Run actions-rs/toolchain@v1
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/
|
Run actions-rs/cargo@v1
virtual workspace defaulting to `resolver = "1"` despite one or more workspace members being on edition 2021 which implies `resolver = "2"`
|
Run actions-rs/cargo@v1:
waku-bindings/src/node/management.rs#L10
unused imports: `handle_json_response`, `handle_response`
|
Run actions-rs/cargo@v1:
waku-bindings/src/node/peers.rs#L11
unused imports: `handle_json_response`, `handle_response`
|
Run actions-rs/cargo@v1:
waku-bindings/src/node/relay.rs#L10
unused import: `handle_json_response`
|
Run actions-rs/cargo@v1:
waku-bindings/src/node/mod.rs#L9
unused import: `Aes256Gcm`
|
Run actions-rs/cargo@v1:
waku-bindings/src/lib.rs#L8
unused import: `rln`
|
Run actions-rs/cargo@v1
`waku-bindings` (lib) generated 5 warnings
|
The logs for this run have expired and are no longer available.
Loading