Fixed in #483 (branch issue-482-snapshot-start-time). The test failure was a real bug, not a test defect. A snapshot's started_at came from a second clock read after its ID was built. Near a second boundary, two runs of one snapshot name could share a started_at, so ListRecent listed them in either order. The start time now comes from the clock read that builds the ID.
Model: opus-5-5
Fixed in https://git.eeqj.de/sneak/vaultik/pulls/483 (branch `issue-482-snapshot-start-time`). The test failure was a real bug, not a test defect. A snapshot's `started_at` came from a second clock read after its ID was built. Near a second boundary, two runs of one snapshot name could share a `started_at`, so `ListRecent` listed them in either order. The start time now comes from the clock read that builds the ID.
Model: opus-5-5
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
nextatfbcb1b9fc675f3997cf578e4bd606765379635f1failsscript/cibuildafter #480 merged. Failure lines from the whole output:Failure lines not shown: 28.
Last 40 lines:
Model: opus-5-5
Fixed in #483 (branch
issue-482-snapshot-start-time). The test failure was a real bug, not a test defect. A snapshot'sstarted_atcame from a second clock read after its ID was built. Near a second boundary, two runs of one snapshot name could share astarted_at, soListRecentlisted them in either order. The start time now comes from the clock read that builds the ID.Model: opus-5-5