Skip to content

Merge main into next: v0.4.0 and the CI fixes from #269 - #270

Merged
T-Crypt merged 5 commits into
nextfrom
T-Crypt/main-into-next
Oct 30, 2026
Merged

T-Crypt merged 5 commits into
nextfrom
T-Crypt/main-into-next

Conversation

@T-Crypt

@T-Crypt T-Crypt commented Oct 30, 2026

Copy link
Copy Markdown
Owner

This brings next up to main. It adds the v0.4.0 release commit and the two CI fixes from #269.

next currently fails TestStrataRequestsReachTheLeaderboard, because its fixture fell outside the engine watcher's 24h request window. Every PR based on next fails CI until this lands, #221 included.

next is an ancestor of main, so the merge has no conflicts. The v0.4.0 notes sit under ## [v0.4.0], and ## [Unreleased] is empty.

When berthd went away mid-run, the listener wrote an unprotected-run
record and then waited to re-attach. If the engine exited in that wait,
Run returned before the listener removed the record. A test that removed
its temp dir right after Run returned failed with "directory not empty",
which turned CI red on main after the v0.4.0 merge.

Run now hangs up the first connection when the engine exits and waits
for the listener to finish before it returns.
The test pinned its requests to 2026-10-28 21:35 MDT. The watcher keeps
24 hours of requests, so from 2026-10-30 03:35 UTC it dropped both rows
and the test failed on every branch. The fixture now sits an hour before
the test runs, with the same zone and microseconds.
fix: turn CI on main green (unprotected record race, stale Strata fixture)
@T-Crypt
T-Crypt merged commit 29857a0 into next Oct 30, 2026
6 checks passed
@T-Crypt
T-Crypt deleted the T-Crypt/main-into-next branch October 31, 2026 02:57
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