Keep feedback correct across retries and revisions #18

Open
opened 2026-07-14 22:32:23 -04:00 by caleb-brown · 0 comments
Owner

What to build

Temper recovers from crashes and ambiguous remote writes while ensuring developers see feedback only for the current intended revision and never receive duplicate external effects.

Acceptance criteria

  • Expired leases, transient dependency failures, bounded exponential retries, terminal failures, and cancellation have explicit state transitions.
  • Publication records desired external effects and reconciles remote state after timeouts or uncertain Forgejo responses.
  • The current Forgejo head is checked immediately before publication; obsolete results are marked stale and never published.
  • A newer revision supersedes older queued or running automatic work without corrupting completed history.
  • An intentional manual rerun remains distinct from duplicate delivery or equivalent automatic intent.
  • Out-of-order events and repeated worker execution converge on one correct Forgejo-visible state.
  • Failure-injection tests cover crashes and ambiguity before and after every external publication effect.

Blocked by

  • #17 — Publish safe inline findings
## What to build Temper recovers from crashes and ambiguous remote writes while ensuring developers see feedback only for the current intended revision and never receive duplicate external effects. ## Acceptance criteria - [ ] Expired leases, transient dependency failures, bounded exponential retries, terminal failures, and cancellation have explicit state transitions. - [ ] Publication records desired external effects and reconciles remote state after timeouts or uncertain Forgejo responses. - [ ] The current Forgejo head is checked immediately before publication; obsolete results are marked stale and never published. - [ ] A newer revision supersedes older queued or running automatic work without corrupting completed history. - [ ] An intentional manual rerun remains distinct from duplicate delivery or equivalent automatic intent. - [ ] Out-of-order events and repeated worker execution converge on one correct Forgejo-visible state. - [ ] Failure-injection tests cover crashes and ambiguity before and after every external publication effect. ## Blocked by - [#17](https://git.caleb-brown.dev/caleb-brown/temper/issues/17) — Publish safe inline findings
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Reference
caleb-brown/temper#18
No description provided.