Skip to content
Continuous Integration

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

Sign in to view logs

Problem: no packet_data and packet_ack in ibc-go v9

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

Triggered via pull request February 12, 2025 09:44
@mmsqemmsqe
opened #103
mmsqe:hexlified
Status Failure
Total duration 3m 11s
Artifacts –

ci.yml

on: pull_request
cargo check
1m 33s
cargo check
cargo test
1m 41s
cargo test
cargo fmt
16s
cargo fmt
cargo clippy
1m 40s
cargo clippy
cargo audit
3m 0s
cargo audit
Fit to window
Zoom out
Zoom in

Annotations

8 errors and 4 warnings
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#L821
this lifetime isn't used in the function definition
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
Unable to publish audit check! Reason: HttpError: Resource not accessible by integration
cargo audit
Critical vulnerabilities were found, marking check as failed
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.