Skip to content

Keepalive: clear a stale implicit skip reason when a request sets a TTL - #29

Merged
cris005 merged 1 commit into
mainfrom
savings/01-implicit-skip-fix
Nov 2, 2026
Merged

cris005 merged 1 commit into
mainfrom
savings/01-implicit-skip-fix

Conversation

@cris005

@cris005 cris005 commented Oct 31, 2026 •

Copy link
Copy Markdown
Contributor

Part 1 of 6 of the savings ledger stack, which replaces #28.

requestSent committed a snapshot that still carried the previous turn's implicit skip reason. The server then dropped the primary messages it had just stored, so the first ping after a learned alias went out without matching the last request.

Wiring the ledger exposed this, but the fix stands on its own: two lines in the engine and two tests.


Stack created with GitHub Stacks CLI • Give Feedback 💬

…s a TTL

requestSent committed a snapshot that still carried the previous turn's
implicit skip reason, so the server dropped the primary messages it had
just stored and the first ping after a learned alias went out unaligned.
@cris005
cris005 added this pull request to stack #35 October 31, 2026 13:27
@sonarqubecloud

Copy link
Copy Markdown

@cris005 cris005 changed the title fix(keepalive): clear a stale implicit skip reason when a request sets a TTL Keepalive: clear a stale implicit skip reason when a request sets a TTL Oct 31, 2026
@cris005
cris005 merged commit ee4ff4a into main Nov 2, 2026
3 checks passed
@cris005
cris005 deleted the savings/01-implicit-skip-fix branch November 2, 2026 05:21
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