The gate keeps a merge it hears before it holds its seat and catches source.main up when it does, so a missed merge no longer leaves the checker on an old trunk (issue 1726)

Conversation 1 Commits 2 Files Changed 5

+236 -4

2 Commits

Author	SHA1	Message	Date
jschoubben	40da368ee3	Date an adopted merge once, by the walk it was adopted from, so a later walk it follows never makes it look newer than a forge merge heard after it (issue 1726, review) mesh/check pass 40da368ee34e on ee216e4e63f1 \| unit 246 run, 4189 kept \| integration 228 run, 4249 kept \| over bound: unit, integration (slowest unit … mesh/delivery delivered Details	2026-10-24 13:55:10 +02:00
jschoubben	15101c9ce6	Move source.main for a merge the gate caught up after a gap, so the checker re-checks open heads on the trunk that is (issue 1726) The checker takes a repository's trunk head only from the gate's source.main. On 2026-10-24 gitea's restarted poll announced mesh-catalog #471's merge while the gate was starting and could not yet tell whether it held the seat; the gate acknowledged the event unread. It then adopted the controller's walk of the merge commit, which carries no merge time, so every older merge of the repository looked newer and source.main was never moved: #472 was checked on the trunk before #471 and its merge refused. - An event heard before the gate can tell whether it holds the seat is offered again, not taken. - An adopted merge is dated by its walk's creation, so it settles into source.main as a forge merge does. - Each time the gate comes to hold the seat it weighs the newest merge of each repository against source.main once more, so a merge marked there and never written (as #471) is written; never backwards.	2026-10-24 13:41:56 +02:00

Author

SHA1

Message

Date

jschoubben

40da368ee3

Date an adopted merge once, by the walk it was adopted from, so a later walk it follows never makes it look newer than a forge merge heard after it (issue 1726, review)

mesh/check pass 40da368ee34e on ee216e4e63f1 | unit 246 run, 4189 kept | integration 228 run, 4249 kept | over bound: unit, integration (slowest unit …

mesh/delivery delivered

Details

2026-10-24 13:55:10 +02:00

jschoubben

15101c9ce6

Move source.main for a merge the gate caught up after a gap, so the checker re-checks open heads on the trunk that is (issue 1726)

The checker takes a repository's trunk head only from the gate's source.main. On 2026-10-24 gitea's
restarted poll announced mesh-catalog #471's merge while the gate was starting and could not yet tell
whether it held the seat; the gate acknowledged the event unread. It then adopted the controller's walk
of the merge commit, which carries no merge time, so every older merge of the repository looked newer
and source.main was never moved: #472 was checked on the trunk before #471 and its merge refused.

- An event heard before the gate can tell whether it holds the seat is offered again, not taken.
- An adopted merge is dated by its walk's creation, so it settles into source.main as a forge merge does.
- Each time the gate comes to hold the seat it weighs the newest merge of each repository against
  source.main once more, so a merge marked there and never written (as #471) is written; never backwards.

2026-10-24 13:41:56 +02:00

The gate keeps a merge it hears before it holds its seat and catches source.main up when it does, so a missed merge no longer leaves the checker on an old trunk (issue 1726) #474