Overview - Ghost

Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
28734
16661ebb Fixed non-deterministic reply ordering when created_at is tied - the replies hasMany relation ordered by created_at ASC only; replies inserted in a tight loop (admin Comments e2e tests) share a millisecond on created_at, so the tie-break was implementation-defined - the new created_at index in the comments-moderation migration exposed this by giving the planner a covering index for the sort, which flipped two reply orderings against the test's implicit assumption about insertion order - pinned ordering to id ASC as a deterministic tie-break, restoring the insertion-order behavior the tests and any client paginating by id rely on
by Steve Larson
Succeeded
28734
b28b3a9d Fixed non-deterministic reply ordering when created_at is tied - the replies hasMany relation ordered by created_at ASC only; replies inserted in a tight loop (admin Comments e2e tests) share a millisecond on created_at, so the tie-break was implementation-defined - the new created_at index in the comments-moderation migration exposed this by giving the planner a covering index for the sort, which flipped two reply orderings against the test's implicit assumption about insertion order - pinned ordering to id ASC as a deterministic tie-break, restoring the insertion-order behavior the tests and any client paginating by id rely on
by Steve Larson
Failed
28734
9e3c79f9 Fixed non-deterministic reply ordering when created_at is tied - the replies hasMany relation ordered by created_at ASC only; replies inserted in a tight loop (admin Comments e2e tests) share a millisecond on created_at, so the tie-break was implementation-defined - the new created_at index in the comments-moderation migration exposed this by giving the planner a covering index for the sort, which flipped two reply orderings against the test's implicit assumption about insertion order - pinned ordering to id ASC as a deterministic tie-break, restoring the insertion-order behavior the tests and any client paginating by id rely on
by Steve Larson
Succeeded
28734
fdb14eaa Fixed non-deterministic reply ordering when created_at is tied - the replies hasMany relation ordered by created_at ASC only; replies inserted in a tight loop (admin Comments e2e tests) share a millisecond on created_at, so the tie-break was implementation-defined - the new created_at index in the comments-moderation migration exposed this by giving the planner a covering index for the sort, which flipped two reply orderings against the test's implicit assumption about insertion order - pinned ordering to id ASC as a deterministic tie-break, restoring the insertion-order behavior the tests and any client paginating by id rely on
by Steve Larson