You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On any error tm2/pkg/bft/node/Node.startRPC leaks all the other created listeners without closing, which can cause simply an irritation for folks trying to restart a node in case the listeners aren't released by the OS directly. This is not a vulnerability but a coding error.
…rror
Once Node.startRPC encounters an error, previously it was discarding
all the created listeners and leaking them unclosed. This change fixes
that using Go's named return values.
Fixesgnolang#3639
…rror
Once Node.startRPC encounters an error, previously it was discarding
all the created listeners and leaking them unclosed. This change fixes
that using Go's named return values.
Fixesgnolang#3639
…rror (#3640)
Once Node.startRPC encounters an error, previously it was discarding all
the created listeners and leaking them unclosed. This change fixes that
using Go's named return values.
Fixes#3639
On any error tm2/pkg/bft/node/Node.startRPC leaks all the other created listeners without closing, which can cause simply an irritation for folks trying to restart a node in case the listeners aren't released by the OS directly. This is not a vulnerability but a coding error.
If we examine this code
gno/tm2/pkg/bft/node/node.go
Lines 716 to 792 in 15d119f
gno/tm2/pkg/bft/node/node.go
Lines 754 to 756 in 15d119f
gno/tm2/pkg/bft/node/node.go
Line 785 in 15d119f
Remedy
We can use named returns to ensure that on any error, all the other listeners are closed.
The text was updated successfully, but these errors were encountered: