Comparing the current account with the drain's missed a switch to another account and back before an answer arrived: a refusal given to the other account then failed the capture. The account listener now counts every change, and a drain stops at the first one. Leaving a capture for its account also dropped the note that a write sent for it may have landed, so discarding it gave no warning. It is kept now. The fake cloud answers as the server does: someone else's strategy is forbidden, and a create under a taken id is a conflict.
Dara Adedeji committed on 10/21/2026, 6:44:36 PMparent1b9c014
Checks
- SuccessfulCodeRabbitGitHub
Review rate limited
- SkippedwebGitHub
- Skippedwindows-testGitHub
- Skippednative-bridgeGitHub
- Skippedwindows-buildGitHub
- Skippedclient-contractGitHub
- Skippednative-replayGitHub
- SkippedanalyzeGitHub
- Skippedpresence-workerGitHub
- Skippedlinux-buildGitHub
- SkippedconvexGitHub
- Successfultest (shard 1)GitHub
- Successfultest (shard 0)GitHub
- SuccessfulchangesGitHub
2 files changedLine totals unavailable