Skip to content

Event listener for Messenger Contracts #105

Event listener for Messenger Contracts

Event listener for Messenger Contracts #105

Triggered via pull request September 18, 2024 02:24
Status Cancelled
Total duration 2m 51s
Artifacts

ci.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

14 errors and 1 warning
lint
golangci-lint exit with code 3
Static Analysis
Canceling since a higher priority waiting request for 'CI-refs/pull/27/merge' exists
Static Analysis: internal/messaging/response_handler.go#L74
G115: integer overflow conversion uint64 -> int64 (gosec)
Static Analysis: internal/messaging/response_handler.go#L192
G115: integer overflow conversion int64 -> int32 (gosec)
Static Analysis: internal/matrix/msg_assembler.go#L49
G115: integer overflow conversion uint -> int (gosec)
Static Analysis: events/listener.go#L524
var-naming: method parameter tokenId should be tokenID (revive)
Static Analysis: events/listener.go#L623
var-naming: method parameter tokenId should be tokenID (revive)
Static Analysis: events/listener.go#L654
var-naming: method parameter tokenId should be tokenID (revive)
Static Analysis: internal/messaging/processor_test.go#L323
unused-parameter: parameter 't' seems to be unused, consider removing or renaming it as _ (revive)
Static Analysis: events/listener.go#L198
S1000: should use a simple channel send/receive instead of `select` with a single case (gosimple)
Static Analysis: events/listener.go#L214
S1000: should use for range instead of for { select {} } (gosimple)
Static Analysis: events/listener.go#L298
S1000: should use a simple channel send/receive instead of `select` with a single case (gosimple)
Unit Tests
Canceling since a higher priority waiting request for 'CI-refs/pull/27/merge' exists
Unit Tests
The operation was canceled.
Check state of go.mod and go.sum
The following actions use a deprecated Node.js version and will be forced to run on node20: actions/checkout@v3, actions/setup-go@v3. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/