You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 3a326f4
Browse filesBrowse the repository at this point in the historyBrowse files
fix(server): stop dropping step reports the timeline path carries
Four defects in the previous three commits.
The record filter whitelisted `Task`, but `type` is optional on the wire
and this same file already treats `Step` as a step 120 lines above, so
every untyped or `Step` record lost its conclusion. Container records are
excluded instead; untyped ones fall back to the parent-id signal the
annotation path uses. The old test sent only `Task` records, so it
asserted the allow-list back at itself; it now sends all three shapes.
The revision column moved into its own migration. Editing an applied
version left any database already at 4 without the column, failing every
step write on an undefined column.
The restore paths never read `revision`, so the counter resumed at zero
and the guard discarded the first writes after a restart -- silently,
since memory stays authoritative until the next one. Seeded from the
persisted maximum, covered by a two-restart test.
The manifest rebuild matched queue rows by (run, job) rather than request
id, attaching the newest queued message to an older attempt and rebuilding
it with step ids its log blobs are not named after. Same attempt-versus-job
confusion as 43c6301.
Reported on #212 by Cubic.
0 commit comments