What the developer wrote
Authored by Oliver Gugger
server: fix linter issue
What changed, and why it matters
This is a one-line code cleanup that silences a Go linter warning by explicitly discarding the return value of a function call. It does not change program behavior or fix any security issue.
No security action needed. Treat as routine code hygiene.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit changes failedMsg.AddInvVect(iv) to _ = failedMsg.AddInvVect(iv) in server.go. This is a purely cosmetic change to satisfy a Go linter (likely errcheck or similar) by acknowledging that the error return value is intentionally ignored. The underlying logic—ignoring the error from AddInvVect—remains identical.
Changed components
server.go OnGetData handlerInspect captured patch +1 / −1
diff --git a/server.go b/server.go
index 15cf2bd..b94abdc 100644
--- a/server.go
+++ b/server.go
@@ -767,7 +767,7 @@ func (sp *serverPeer) OnGetData(_ *peer.Peer, msg *wire.MsgGetData) {
err := sp.server.pushInventory(sp, iv, doneChan)
if err != nil {
- failedMsg.AddInvVect(iv)
+ _ = failedMsg.AddInvVect(iv)
}
// Move to the next item if we haven't processed 5 times yet.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.