Repository navigation
tape: unit tests for Script.lacks/lacksName; tour caption when frost comes first - #966
fizzy-linux[bot] wants to merge 3 commits into
Conversation
PM note: how this PR will be handledWhat it is for: linux: work-566 Rules that apply: none special. Things to watch (checked by rule):
What happens next:
A living status comment below is kept current. Nothing here is a merge decision. |
Where this PR standsStage: Author's turn What the PM needs before approving (ticks as it is met; the full CI runs only at the end, after the reviews are clean):
Rules that apply: touches the SDK or plugin ABI: the shape fingerprint must be recorded. Reviews at the current commit (
3 earlier reviews are for older commits and will be redone. Latest fixes comment: https://github.com/fizzyedit/work/issues/625#issuecomment-6478575795 (1 finding answered) Updated 2026-10-28 20:54 UTC by the PM. This comment is edited in place. |
Agent-Team: linux Worker: codex
Agent-Team: linux Worker: codex
|
Closed by the PM (2026-10-30): this work already merged in another PR (named in its work thread), so this one is superseded. No change needed from the author. |
Part of fizzyedit/work#566
Rework: work#670
In plain words
A connection test could wait forever on Windows after receiving its reply. It now checks that fizzy ends the connection while the other end stays open, avoiding an unreliable Windows notification.
What you will notice
Nothing visible: internal test reliability.
How this serves fizzy
Goal: one codebase, every platform; reliable Windows checks help keep the same behavior across platforms.
Goal
Answer windows/codex F1 on PR #966 at f69e01f (fizzyedit/work#670).
What changed and why
UpgradePeer reads the four expected reply bytes and waits for explicit release instead of EOF. The test checks the complete reply and link termination before releasing the peer, so peer disconnect cannot satisfy the app-close assertion. Error cleanup stops the server and joins the peer before freeing the link. app/AGENTS.md documents intermittent Windows AF_UNIX EOF hangs; the test watchdog calls abort after 60 seconds, consistent with the reported exit code 3. This is a plausible cause, not a reproduced Windows diagnosis.
How it was verified
Formatting, lint (3/3 steps), and native build (85/85) pass. Unit tests: 187/189 steps; integration: 97/100 steps, with socket restrictions. See GATES.md for exact gate results and an earlier transient headless save/close assertion that passed on rerun. Socket creation is denied here, including in the changed test; an unrestricted Windows rerun is necessary. No UI or production behavior changes. Without app close, the revised test keeps the client open and fails its link termination assertion rather than allowing client disconnect to satisfy it; this mutation cannot be exercised in this sandbox.
Not done / follow-ups
Harness must commit, push, and post the FIXES response with the new head. Windows must rerun the reported failing gate; no Windows runtime is available here. No GitHub operations were attempted, per the worker contract.
Changes (8 files, +84/-802)
Gates: 6 of 6 passed
scripts/check-fmt.sh(exit 0)scripts/zb build --summary all(exit 0)scripts/zb build test --summary all(exit 0)scripts/zb build test-integration --summary all(exit 0)scripts/zb build check-web --summary all(exit 0)scripts/zb build test-sdk-version --summary all(exit 0)