Relationships
#4853 serve: a follower that does not name its leader tells an inFlight serve_not_leader caller to try again
Opened by stack72 · 11/18/2026· Shipped 11/18/2026
src/serve/leader_link.ts notLeaderResponse replaces the refusal's message with 'This serve node does not lead the datastore; try again' whenever nameLeader is false, including when the refusal is inFlight (the forward reached the leader, which may have acted). ServeNotLeaderError's own inFlight message says the request may already have run and to check its outcome before retrying; the replacement drops that and invites a blind retry. Expected: an inFlight refusal keeps a message saying the outcome is unknown even when the leader is not named. The HTTP client (packages/client) overrides the message for inFlight replies after swamp-club#4830, but the WebSocket path and any other reader still see 'try again'. Found while fixing swamp-club#4830.
Shipped
Click a lifecycle step above to view its details.
Sign in to post a ripple.