Skip to content

Carry an unattended fail-closed deny to the gateway on the next PostToolUse (#25 re-landed on main) - #30

Merged
davidcrowe merged 1 commit into
mainfrom
fix/690-carry-fail-closed-on-main
Sep 8, 2026
Merged

Carry an unattended fail-closed deny to the gateway on the next PostToolUse (#25 re-landed on main)#30
davidcrowe merged 1 commit into
mainfrom
fix/690-carry-fail-closed-on-main

Conversation

@davidcrowe

Copy link
Copy Markdown
Collaborator

PR #25 was squash-merged into its stacked base branch fix/relay-warning after #24 had already merged, so its change never reached main. This is that squash commit (b024934) cherry-picked onto current main. Tests green locally.

…oolUse (gatewaystack-connect#690 fix 3) (#25)

The interactive fail-open branch has queued its lapse for the session's
next PostToolUse since 0.14.0; the unattended fail-closed branch recorded
nothing, so a call this client blocked while the gateway was answering
allow left the two ledgers disagreeing with no way to see it. Same lapse
log (posture: closed) and same per-session carry, with the detail marked
so the gateway's row says blocked client-side, not ran ungoverned.

(cherry picked from commit b024934)
@davidcrowe
davidcrowe merged commit 69ab74e into main Sep 8, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant