From e0dc742e175a576e7e9c37fb3c92c3cd2a4ab1de Mon Sep 17 00:00:00 2001 From: Matt Richardson Date: Mon, 19 Oct 2026 16:30:43 -0400 Subject: [PATCH] Shorten rebindLocked's header - the rationale for Wire's first attempt and its reload callback being the same call is one sentence, not five Co-Authored-By: Claude Opus 5.5 --- localapi/endpoint.go | 8 ++------ 1 file changed, 2 insertions(+), 6 deletions(-) diff --git a/localapi/endpoint.go b/localapi/endpoint.go index 2739b93a..8788d0f3 100644 --- a/localapi/endpoint.go +++ b/localapi/endpoint.go @@ -51,12 +51,8 @@ func (e *endpoint) Path() string { } // rebindLocked brings the endpoint up at path with acc, moves it there, or, when it is -// already there, applies a changed access. It is the one place a socket is installed and -// the one way an endpoint comes up, so Wire's first attempt and its reload callback are -// the same call, and an endpoint already at path is left as it is: Wire registers the -// callback before the first attempt, so a HUP that lands between the two has the -// callback do the first bind, and the first attempt then finds the socket it was about -// to create already up. +// already there, applies a changed access; with nothing changed it does nothing, which +// is what lets Wire's first attempt and its reload callback be the same call. // // The new socket is bound before the old one is given up: a bad path in a reloaded // config leaves the operator with the endpoint they already had rather than none. serve