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
Deploy #702 PR3b (#1832) only 24h after the attempt journal (#1824, 000161) is live in each environment #1835
#1832 (#702 PR3b) lifts the refusal of Redshift re-drive and Retry. A Redshift purchase row dispatched before the attempt journal (#1824, migration 000161) was live in an environment has no journal record. If AWS changes that tuple's offering within the 24h re-drive horizon, a retry of such a row could buy a second reserved node. So in every environment, #1832 must be deployed no earlier than 24h after #1824 and 000161 are live there.
Dev is handled by merge timing: #1824 went live on dev at 2026-11-06T23:38:42Z, so #1832 merges no earlier than 2026-11-07T23:39Z. Prod deploys separately, so the same rule needs an explicit runbook step.
The prod (and any other environment's) release process makes sure #1832 is deployed at least 24h after #1824 and migration 000161 are live in that environment.
Add one line to known_issues/39_redshift_dedupe_window.md recording the ordering and why.
Optional, for a later change: a fail-closed check that refuses a Redshift retry of a row whose first dispatch predates the environment's journal start time.
Claimed by claude-darling: local commits (docs change: DEPLOYMENT.md release-ordering step plus a line in known_issues/39). Premise re-checked on main: neither file records the 24h ordering, #1824 (000161) and #1832 are both merged. Platform is at its PR cap, so this stays local until a slot opens.
Claimed by claude-darling: committed locally (docs only: DEPLOYMENT.md release-ordering step with the two-deploy procedure and rollback note, plus a line in known_issues/39). Two adversarial review passes closed. Will push and open the PR when platform has a PR slot.
Activity
cristim commentedon Nov 9, 2026
Claimed by claude-darling: local commits (docs change: DEPLOYMENT.md release-ordering step plus a line in known_issues/39). Premise re-checked on main: neither file records the 24h ordering, #1824 (000161) and #1832 are both merged. Platform is at its PR cap, so this stays local until a slot opens.
cristim commentedon Nov 9, 2026
Claimed by claude-darling: committed locally (docs only: DEPLOYMENT.md release-ordering step with the two-deploy procedure and rollback note, plus a line in known_issues/39). Two adversarial review passes closed. Will push and open the PR when platform has a PR slot.
docs(deploy): start the 24h clock at the confirmed migration and say …
docs(deploy): order the Redshift re-drive release after the attempt j…