Skip to content

feat: backport substrate code from relayer #4

feat: backport substrate code from relayer

feat: backport substrate code from relayer #4

Triggered via pull request October 2, 2023 14:49
Status Failure
Total duration 1m 4s
Artifacts

checks.yml

on: pull_request
linter-check
54s
linter-check
vet-check
41s
vet-check
Fit to window
Zoom out
Zoom in

Annotations

10 errors and 2 warnings
vet-check: chains/substrate/connection/connection.go#L77
undefined: state.NewProvider
vet-check: chains/substrate/executor/message-handler_test.go#L80
ExampleMessageHandler should be niladic
vet-check: chains/substrate/executor/message-handler_test.go#L80
ExampleMessageHandler should return nothing
vet-check: chains/substrate/executor/message-handler_test.go#L80
ExampleMessageHandler refers to unknown identifier: MessageHandler
vet-check
Process completed with exit code 1.
linter-check: chains/substrate/connection/connection.go#L77
undefined: state.NewProvider (typecheck)
linter-check: chains/substrate/client/client.go#L14
could not import github.com/ChainSafe/sygma-core/chains/substrate/connection (-: # github.com/ChainSafe/sygma-core/chains/substrate/connection
linter-check: chains/substrate/connection/connection.go#L77
undefined: state.NewProvider) (typecheck)
linter-check: chains/substrate/executor/message-handler_test.go#L80
tests: ExampleMessageHandler should be niladic (govet)
linter-check
Process completed with exit code 1.
vet-check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
linter-check
The following actions uses node12 which is deprecated and will be forced to run on node16: actions/setup-go@v2, actions/checkout@v2. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/