Skip to content
build

bug: propagate TLS errors as failures #311

Sign in to view logs

bug: propagate TLS errors as failures

bug: propagate TLS errors as failures #311

Triggered via pull request April 24, 2024 16:07
@ainghazalainghazal
synchronize #73
ainghazal:bug/tls-errors
Status Success
Total duration 51s
Artifacts –

build.yml

on: pull_request
short-tests
31s
short-tests
lint
3s
lint
gosec
42s
gosec
coverage-threshold
32s
coverage-threshold
integration
30s
integration
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
lint: internal/model/packet_test.go#L380
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/mocks/addr.go#L1
should have a package comment
lint: internal/tlssession/tlshandshake_test.go#L456
error var tlsFactoryError should have name of the form errFoo
lint: internal/runtimex/runtimex_test.go#L13
parameter 't' seems to be unused, consider removing or renaming it as _
lint: internal/model/mocks.go#L44
exported function NewTestLogger should have comment or be unexported
lint: internal/model/session.go#L8
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/reliabletransport/constants.go#L25
don't use ALL_CAPS in Go names; use CamelCase
lint: internal/bytesx/bytesx.go#L38
comment on exported function GenRandomBytes should be of the form "GenRandomBytes ..."
lint: internal/tlssession/tlshandshake_test.go#L524
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 _