ci(fork): move to a new concurrency generation by omegent-app[bot] · Pull Request #369 · patroza/t3code

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-app · 2026-08-07T04:36:19Z

Concurrency: new generation

Last night's push run for 15a0c5d59 is wedged. GitHub refuses to cancel it:

409 Cannot cancel a workflow re-run that has not yet queued.

That state came from my own re-run request while diagnosing the runner outage — worth owning,
since it is what turned a stalled run into an uncancellable one. It holds its concurrency group
indefinitely, and the current fork/dev tip 009b3f9c6 has no run at all as a result.

Prefixing the group with a generation — ci-v2- — puts new runs in a fresh namespace where nothing
can queue behind the wedged run. Nothing depends on the literal value; bump it again if this recurs.

Unchanged: per-SHA keying and no-cancel-on-push. A push run's conclusion is what approves that commit
for deployment, so cancelling one as superseded would leave that SHA unapprovable.

Macroscope

Withdrawn: the config stays. .macroscope/ was removed in the first commit and restored in the
second, per review — the branch nets to no Macroscope change.

After this merges

009b3f9c6 still has no run, and the poller only promotes a SHA with a successful fork-ci push
run — so the fleet stays where it is until a push lands under the new key. Merging this is itself
such a push, which should produce the first ci-v2- run and unblock the queue.

Co-authored by @patroza

opened by Patrick Roza in chat thread Discord · Discord · T3

Last night's push run for 15a0c5d is wedged. GitHub refuses to cancel it -- "Cannot cancel a workflow re-run that has not yet queued", a state my own re-run request put it in -- so it holds its concurrency group indefinitely and the current fork/dev tip 009b3f9 never got a run at all. Prefix the group with a generation, ci-v2-. New runs land in a fresh namespace and cannot queue behind anything wedged under the old key. Nothing depends on the literal value; bump it again if this recurs. The per-SHA keying and the no-cancel-on-push rule are unchanged: a push run's conclusion is what approves that commit for deployment, so cancelling one as superseded would leave that SHA unapprovable. Also remove .macroscope, which configured the Effect Service Conventions check run agent. That disables the custom agent only. Macroscope's built-in checks come from the installed GitHub App, so the app has to be uninstalled from the repository to stop them; it had already been reporting "Skipped -- billing issue" on pull requests. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-appBotand others added 2 commits August 7, 2026 04:35

ci(fork): keep the Macroscope config after all
2ab87ac
Restores .macroscope/ removed one commit earlier; the check-run agent stays. Co-authored-by: Patrick Roza <42661+patroza@users.noreply.github.com>

omegent-appBot changed the title ~~ci(fork): move to a new concurrency generation, drop Macroscope~~ci(fork): move to a new concurrency generationAug 7, 2026

patroza merged commit b8df938 into fork/devAug 7, 2026
4 checks passed

patroza mentioned this pull request Aug 7, 2026
sync(upstream): adopt user-anchored thread pagination into fork/dev #371
Closed