mirror of
https://github.com/rennf93/roboco.git
synced 2026-08-03 07:23:24 +02:00
[sweep] strip Fxxx audit-ID tokens + trim bloated comments/docstrings + add behavior-change docs
Post-audit sweep over the 135 audit-fix commits since19a474d3: 1. Stripped every # Fxxx: audit-ID token from comments AND every Fxxx token from docstring openings across 211 blocks / ~626 lines. The CEO flagged these twice: audit-issue IDs in code confuse future devs/agents. The descriptive text is preserved; only the Fxxx token is removed (and bloated narrative blocks trimmed to 1-3 lines keeping the one non-obvious invariant). 2. Trimmed bloated comments/docstrings to the concise standard (1-3 lines). 3. Added missing behavior-change docs for the audit-fix batch: prompts/roles (documenter, pr_reviewer, qa), user-facing docs (api auth, websockets, agent-gateway, megatask, merge-model, task-lifecycle, grok, resilience, conventions, panel, security, troubleshooting), and the RAG corpus (cell-pm, main-pm, pr-reviewer, qa roles; conventions; messaging-tools; escalation; megatask; task-claiming workflows). Comment/docstring/prose ONLY — zero code-line edits (verified: the diff contains no def/class/return/if/for/await/assignment/call lines). Gates green: ruff format + ruff check clean, mypy clean on roboco/. The only pytest failures are the pre-existing sync_branch tracing-decision gap (B1,250be5c2) — not sweep-caused and tracked separately.
This commit is contained in:
@@ -1,12 +1,6 @@
|
||||
"""F013 — concurrent approve races on the shared release clone.
|
||||
|
||||
The approve flow ran the ~40min ``ReleaseExecutor.execute`` with no guard, so
|
||||
two concurrent CEO ``POST /proposal/approve`` calls (double-click, panel retry)
|
||||
both found the same held proposal and raced on the shared, ``rm -rf``'d writable
|
||||
release clone — interleaving ``git add``/``commit``/``push`` and corrupting the
|
||||
release. The fix acquires a Redis ``SET NX`` mutex keyed by the proposal id
|
||||
before execute (TTL > the 40min CI ceiling) and releases it on completion; a
|
||||
second concurrent approve sees the lock held and refuses instead of racing.
|
||||
"""Concurrent CEO approve races on the shared release clone are serialized by a
|
||||
Redis ``SET NX`` mutex keyed by the proposal id; a second concurrent approve
|
||||
sees the lock held and refuses instead of racing on the writable clone.
|
||||
"""
|
||||
|
||||
from __future__ import annotations
|
||||
|
||||
Reference in New Issue
Block a user