cleanup: fix vet and staticcheck failures

[iand]

Fixes the safe staticcheck failures. The following remain and need more thought or explicit ignores.

May indicate a bug, not clear what the intention is here:

gossipsub.go:904:4: ineffective break statement. Did you mean to break out of the outer loop? (SA4011)

Needs a decision on the alternative:

gossipsub.go:1300:8: log.EventBegin is deprecated: Stop using go-log for event logging  (SA1019)

Changing these may break clients who rely on error string text:

validation.go:146:15: error strings should not be capitalized (ST1005)
validation.go:173:15: error strings should not be capitalized (ST1005)
validation.go:209:15: error strings should not be capitalized (ST1005)
validation.go:387:9: error strings should not be capitalized (ST1005)

[vyzo]

gossipsub.go:904:4: ineffective break statement

That thing with the break is really innocuous, we can just remove it.

gossipsub.go:1300:8: log.EventBegin is deprecated: Stop using go-log for event logging (SA1019)

We can just replace it with a log.Infow that logs the timing

Changing these may break clients who rely on error string text:

That's just silly/stupid; just go ahead and change them.

[vyzo]

maybe add some short-circuit code for breaking the test when we have goroutines failing? Or wait for them. Not sure what's prudent.

[iand]

breaking

Is this a reference to the replacement of t.Fatal with t.Error+return in test goroutines? In these cases the test still fails.

[vyzo]

yeah, just worried it might get blocked somewhere.

…

On Mon, Jul 19, 2021, 15:55 Ian Davis ***@***.***> wrote: breaking Is this a reference to the replacement of t.Fatal with t.Error+return in test goroutines? In these cases the test still fails. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#435 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAI4STAYF6ZDBKPD2PIAN3TYQOCXANCNFSM5ATQVWAA> .

[iand]

yeah, just worried it might get blocked somewhere.

OK. In TestGossipsubAttackSpamIHAVE returning from the goroutine cancels the context. I could use that to ensure that the other goroutines exit too (we should do that anyway to avoid other sources of blocking). Will look at the other tests as well.

[iand]

yeah, just worried it might get blocked somewhere.

OK. In TestGossipsubAttackSpamIHAVE returning from the goroutine cancels the context. I could use that to ensure that the other goroutines exit too (we should do that anyway to avoid other sources of blocking). Will look at the other tests as well.

Done this in 4238ca7