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
review fixes: migration must not feed the recovery tracker
The tracker's entries close on the next provider-originated ingress
for the destination -- and after a migration the OLD exit is alive and
delivering until the server validates the new path, so every entry
closed milliseconds later as a fake ~0s recovery and a fake
rebindsAccepted: the two headline metrics this program is judged by,
corrupted by the mechanism built to improve them. Migration arms
nothing now; the [rel] migrate line is its field signal.
Also: remaining counts flows genuinely still riding the exit (the
pre-sweep subtraction counted stale book entries as stayers), and the
seam wiring is pinned by source anchors -- deleting the two wiring
lines previously failed no test.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
t.Errorf("the migration seam is wired %d time(s), want 2 (quality and speed windows): an unwired seam makes every drain a deadline teardown again", got)
317
327
}
318
328
ifgot:=nextWarningCall(`printStats("client health warning")`); got!="setWarning(remove, warnUnhealthy)" {
319
329
t.Errorf("the health-warning branch warns with %q, want the rank-derived setWarning(remove, warnUnhealthy)", got)
0 commit comments