Skip to content

bug: propagate TLS errors as failures #310

bug: propagate TLS errors as failures

bug: propagate TLS errors as failures #310

Triggered via pull request April 15, 2024 15:07
Status Success
Total duration 52s
Artifacts

build.yml

on: pull_request
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
lint: internal/runtimex/runtimex_test.go#L22
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/runtimex/runtimex_test.go#L13
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/runtimex/runtimex_test.go#L40
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/runtimex/runtimex_test.go#L31
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/model/packet.go#L25
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/model/packet.go#L24
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/model/session.go#L8
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/model/packet.go#L26
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/model/packet.go#L27
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/model/session.go#L11
don't use ALL_CAPS in Go names; use CamelCase