Skip to content

fix(desktop): preserve group turn custody through Stop and rename races - #127

Draft
RecursiveIntell wants to merge 2 commits into
mainfrom
fix/ares-group-lifecycle-custody-20261004
Draft

RecursiveIntell wants to merge 2 commits into
mainfrom
fix/ares-group-lifecycle-custody-20261004

Conversation

@RecursiveIntell

Copy link
Copy Markdown
Owner

Group turns could lose accepted custody on a typed hold or interrupt ACK, wait for an execution worker after becoming terminal, or lose their collector across a rename. Preserve the captured turn until exact retirement, fence successor admission while any session interrupt is pending, and let terminal collection finish without reserving another worker. Stop now shows whether cancellation remains unconfirmed or turns are still retiring; approval success requires a positive resolved count.

Renames rehome the existing lifetime and commit all local membership/room/navigation intent before metadata awaits. Delayed settings saves follow the current lifetime and cannot recreate a deleted name or update a replacement room. Existing admission, durable receipt and backend ownership remain intact.

Validation: 152 focused offline cases pass against the exact production plugin through fake ports, including 12 pending-interrupt and overlapping/stale-settings counterexamples. Independent exact-source review passed. Forward/reverse patches are verified against pinned preimages and postimages. Core exact-head CI remains the next gate; live-provider cancellation, host-global capacity and installed-app activation were not exercised.

Draft source proposal only; not installed or activated. Revert this focused commit for rollback; exact reverse patch SHA256 f1a2e23749e23940e7cd8af59d8a2ed8572dff2004aacf6da3c59d2dda1c4563 restores the pinned base from these postimages. The four-worker limit is per room, not a host-wide capacity claim.

@github-actions

github-actions Bot commented Oct 4, 2026 •

Copy link
Copy Markdown

૮ >ﻌ< ა ci review

ran on b4b752d — fix(desktop): reconcile group cancellation preparation and a

⚠️ Warnings

OSV vulnerability scan · View job

96 known vulnerabilities found in pinned dependencies.

How to fix:

Review the findings in the Security tab. Update the affected dependencies if a patched version is available.


debug info

CI timings

CI timings · View report · View job

Wall time 4m30s vs 7m23s (-39.1%). 8 job(s) slower, 11 faster,

  • JS & TS checks / ui-tui/packages/hermes-ink / check: -90.0s
  • JS & TS checks / apps/desktop / check:test:ui:shard-2of3: -77.0s
  • JS & TS checks / apps/desktop / check:test:ui:shard-1of3: +22.0s
  • JS & TS checks / web / check: -19.0s
  • JS & TS checks / apps/desktop / check:test:desktop:all: -18.0s

Copy link
Copy Markdown
Owner Author

Reviewed follow-up to original failed hosted plugin job. The original seven assertion failures and 4 GiB heap OOM remain retained evidence.

Preparation-time Stop now fences cancellation confirmation while preparation remains pending. A proven prompt admission refusal releases unused custody after preparation settles, with refusal state reset before each actual retry. Existing fixtures distinguish interrupt acknowledgement from terminal retirement; a bounded one-shot Stop fixture removes its own repeated-poll feedback.

Accepted offline receipt: 346/346 cases across 12 files, independent review accepted, exact forward/reverse replay. The original hosted OOM cause remains unqualified until fresh hosted CI. No installed app, backend/provider or live Ares execution occurred. Revert follow-up commit to restore prior head b4e6c5859e27b6495d7387279fdefd2012bc2ff1.

Published head b4b752d2e62222163a232595f021e2a5f1e3e255, tree c5a1d8b334e36662d153e620e6308080bce80ed6: all 12 remote changed-file blobs verified. PR remains draft.

Copy link
Copy Markdown
Owner Author

Published follow-up head b4b752d2e62222163a232595f021e2a5f1e3e255: hosted desktop plugin checks now pass and the required-check aggregate reports success. The separate Nix flake check failed.

Its managed-guard builder log reports echo: write error: Broken pipe followed by FAIL: config set not guarded, while also printing the managed nixos installation refusal. This observation does not establish a guard bypass or a source root cause. No Nix/check/protection changes or reruns were made by publication. Keep this failure as an unresolved qualification gate; the green aggregate alone does not mean every check passed.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant