Skip to content

Problem: no packet_data and packet_ack in ibc-go v9 #120

Problem: no packet_data and packet_ack in ibc-go v9

Problem: no packet_data and packet_ack in ibc-go v9 #120

Triggered via pull request February 12, 2025 14:52
@mmsqemmsqe
synchronize #103
mmsqe:hexlified
Status Failure
Total duration 47s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 4 warnings
cargo audit
Unable to publish audit check! Reason: HttpError: Resource not accessible by integration
cargo audit
Critical vulnerabilities were found, marking check as failed
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L192
this lifetime isn't used in the function definition
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L227
this lifetime isn't used in the function definition
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L303
this lifetime isn't used in the function definition
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L822
this lifetime isn't used in the function definition
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L1243
called `unwrap` on `attribute` after checking its variant with `is_some`
cargo clippy: solo-machine-core/src/service/ibc_service.rs#L1245
called `unwrap` on `attribute` after checking its variant with `is_some`
cargo clippy: solo-machine-core/src/signer.rs#L51
the following explicit lifetimes could be elided: 'a
cargo clippy
Process completed with exit code 101.
cargo audit
2 vulnerabilities found!
cargo audit
7 warnings found!
cargo audit
It seems that this Action is executed from the forked repository.
cargo audit
GitHub Actions are not allowed to use Check API, when executed for a forked repos. See https://github.com/actions-rs/clippy-check/issues/2 for details.