tr
TryGhost
GitHub
Ghost
Workspace
GitHub
CI Pipeline Executions
Filtered
Runs
Demo
Insights
Compare tasks
Analytics
Sign in
Toggle sidebar
Overview
⌘K
Ghost
Loading workspace stats
Loading workspace insights...
Statistics interval
7 days
30 days
Latest CI Pipeline Executions
Status
Fix filter
Filter
Fuzzy
Filter range
Sort by
Sort by
Start time
Sort ascending
Sort descending
GitHub
Ghost
Workspace
Succeeded
30369
59af9a77 Fixed flaky access settings dropdown gesture no ref `choose()` clicked a select trigger, clicked an option, and returned. Choosing an option starts Radix's close but does not finish it: measured at the instant the helper returns, the option list is still mounted and the body still carries `pointer-events: none`. Everything the caller does next races that teardown. Losing the race fails in two ways, both silent at the point of the mistake. A click can be refused outright — Playwright waits for pointer events the body is suppressing and times out — or it can open a layer that the teardown then dismisses, so the next dropdown never opens and the failure only surfaces at the assertion that waits for its options. The second is what CI hit: "Matcher did not succeed in time" on the tier option after the tiers combobox was clicked open. `choose()` now waits for the dropdown to unmount, which also restores the body's pointer events. The same shape exists at roughly twenty other call sites across the suite, but not all of those dropdowns are single-select — the bulk-actions label picker stays open by design — so each needs classifying rather than a blanket sweep. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Ekc7dHMu3xDE7um1zNkaN
by Claude
C
Failed
30369
cf0cee06 Fixed flaky tier checkout acceptance assertions no ref The tier detail modal's Save commits two resources in sequence: the tier itself, then the checkout configuration. `handleSave` flips the button to "Saved" as soon as the tier write resolves, and only then does `onOk` call the checkout section's save. Two specs waited on "Saved" and read the checkout capture synchronously on the next line, so they asserted against a request that had not necessarily been issued yet. That race was the single largest source of admin acceptance failures on main: it accounted for every failing run sampled over the last two days, surfacing either as `Cannot read properties of undefined (reading 'tiers_checkout_config')` or `expected [] to have a length of 1`. Both now poll the capture, matching the sibling spec in the same file that already does. Reproduced by delaying the checkout write, which fails both specs with the exact CI errors and passes with this change. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019Ekc7dHMu3xDE7um1zNkaN
by Claude
C
Previous
Next