Development record
After abcd land's own push moves a branch, the post-push wait re-reads the pull request until the forge shows the pushed commit, for up to 30 s of pauses. When someone else pushes to the branch straight after, the forge settles on a third head that will never equal the pushed one, and land waits the whole 30 s before it stops with its 'pull the forge's head' remedy. Nothing unsafe follows, since land never arms a head it did not gate, but the stop arrives 30 s late. Found by the Opus reviewer of the forge-lag fix (iss-2610151855227496), 2026-10-16.
issueopenminoriss-2610160315304959
After abcd land's own push moves a branch, the post-push wait re-reads the pull request until the forge shows the pushed commit, for up to 30 s of pauses. When someone else pushes to the branch straight after, the forge settles on a third head that will never equal the pushed one, and land waits the whole 30 s before it stops with its 'pull the forge's head' remedy. Nothing unsafe follows, since land never arms a head it did not gate, but the stop arrives 30 s late. Found by the Opus reviewer of the forge-lag fix (iss-2610151855227496), 2026-10-16.
Frontmatter
| id | iss-2610160315304959 |
|---|---|
| type | issue |
| lifecycle | open |
| severity | minor |
.abcd/work/issues/open/iss-2610160315304959-after-abcd-land-s-own-push-moves-a.md
open on GitHub ↗ · commit history ↗
mentions1
- iss-2610151855227496abcd land's single run, push and then queue, stops on its most common path. On 2026-10-15 it pushed feat/abcd-land at 2abcab16c (18:54:26Z), then in the same run read pull request #1020 and the forge still reported the old head 572cd8c0f, so the enqueue step stopped with 'wait for the forge to see the push' and nothing was armed. A re-run 12 seconds later armed it. Refusing to arm on a stale head is the safe failure and stays, but since a push that moves the head is the normal case, the person must usually run abcd land twice. Found by a real run; the fake forge answers at once, so no test could show it.