Overview - Ghost

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
30686
a87c3a41 Changed Mailgun config reads to validate and capped backfills to persist ref https://linear.app/ghost/issue/BER-3936/raise-mailgun-event-fetch-throughput-concurrent-paging-logs-api The Mailgun config reader cast whatever config and settings held into the shape it needed, so a partial block reached the transports as if it were complete. It now validates both sources at the boundary; an invalid block disables Mailgun with a warning instead of silently falling back to settings. Fetch results also report whether the fetcher stopped early, so a scheduled backfill that read filtered records without delivering any events keeps its schedule instead of being cleared as finished.
by Jonatan Sv...
J
Succeeded
30686
f74cfcd9 Changed Mailgun config reads to validate and capped backfills to persist ref https://linear.app/ghost/issue/BER-3936/raise-mailgun-event-fetch-throughput-concurrent-paging-logs-api The Mailgun config reader cast whatever config and settings held into the shape it needed, so a partial block reached the transports as if it were complete. It now validates both sources at the boundary; an invalid block disables Mailgun with a warning instead of silently falling back to settings. Fetch results also report whether the fetcher stopped early, so a scheduled backfill that read filtered records without delivering any events keeps its schedule instead of being cleared as finished.
by Jonatan Sv...
J
Succeeded
30686
7f6afc6f Changed Mailgun config reads to validate and capped backfills to persist ref https://linear.app/ghost/issue/BER-3936/raise-mailgun-event-fetch-throughput-concurrent-paging-logs-api The Mailgun config reader cast whatever config and settings held into the shape it needed, so a partial block reached the transports as if it were complete. It now validates both sources at the boundary; an invalid block disables Mailgun with a warning instead of silently falling back to settings. Fetch results also report whether the fetcher stopped early, so a scheduled backfill that read filtered records without delivering any events keeps its schedule instead of being cleared as finished.
by Jonatan Sv...
J
Succeeded
30686
75501f6a Changed Mailgun Logs ingestion to skip unreadable records and bound paging ref https://linear.app/ghost/issue/BER-3936/raise-mailgun-event-fetch-throughput-concurrent-paging-logs-api Review found several ways one provider response could stall every analytics lane: a single record the adapter could not read threw and reset the cursor on every cycle, a repeated pagination token did the same, an empty page that still carried a token ended the domain and let the cursor advance past unfetched events, and a page consisting only of other sites' records did not count toward the per-domain budget, so a low-volume site on a busy shared domain could page through the whole account window serially. Pages and records are now validated with Zod at the boundary. An unreadable record is skipped and counted in a warning, records the provider returns count toward the budget whether or not they match, a domain stops after a fixed number of pages, an empty page with a token is followed, and a repeated token ends the domain without delivering the repeated page. Whenever a domain stops early its cursor rests on the latest record it covered, which was either processed or irrelevant, so the next fetch continues rather than skips. The Logs endpoint keeps a proxy prefix from the configured base URL, a rejected key explains that account log access is required, each domain logs the same processed/status/cursor summary as the Events path, and the parity fixture now covers a permanent failure's severity and delivery status.
by Jonatan Sv...
J
Succeeded
30686
60abc15e Added selectable Mailgun Logs analytics ingestion ref https://linear.app/ghost/issue/BER-3936/raise-mailgun-event-fetch-throughput-concurrent-paging-logs-api Keep Events as the default while allowing Logs to use the same configuration, sending domains, event shape and timestamp cursors. Preserve serial callbacks, boundary overlap and domain-safe progress so API selection can be evaluated independently of counter rollout and scheduling policy. Document the live credential and provider parity checks required before opt-in.
by Jonatan Sv...
J