stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Retry edited offline issue captures with a fresh idempotency key #283

New Issue
Closed
opened 2026-08-08 08:56:47 +00:00 by timmy · 0 comments
timmy commented 2026-08-08 08:56:47 +00:00
Owner
Copy Link

Problem

Editing a queued offline issue after a permanent validation failure preserves its original idempotency key. Because the server fingerprints the request payload, delivering the corrected payload with that consumed key returns a conflict instead of creating the issue.

Evidence

frontend/issue-outbox.js keeps operationId in update(), and the current edit/retry test explicitly expects the same key before and after changing the title. Historical issue/PR titles and recent commits contain offline capture, durable admission, and retry idempotency work, but no payload-edit key rotation.

Acceptance criteria

  • Changing any delivery field rotates the operation ID while preserving the stable outbox item ID.
  • Saving an identical payload preserves the operation ID.
  • Attention/error state clears after an edit.
  • Durable edits reconcile the replacement before Background Sync registration.
  • Foreground retry delivers the edited payload with the replacement key exactly once.

Implementation must follow strict RED-GREEN TDD.

## Problem Editing a queued offline issue after a permanent validation failure preserves its original idempotency key. Because the server fingerprints the request payload, delivering the corrected payload with that consumed key returns a conflict instead of creating the issue. ## Evidence frontend/issue-outbox.js keeps operationId in update(), and the current edit/retry test explicitly expects the same key before and after changing the title. Historical issue/PR titles and recent commits contain offline capture, durable admission, and retry idempotency work, but no payload-edit key rotation. ## Acceptance criteria - Changing any delivery field rotates the operation ID while preserving the stable outbox item ID. - Saving an identical payload preserves the operation ID. - Attention/error state clears after an edit. - Durable edits reconcile the replacement before Background Sync registration. - Foreground retry delivers the edited payload with the replacement key exactly once. Implementation must follow strict RED-GREEN TDD.
timmy self-assigned this 2026-08-08 08:56:47 +00:00
timmy closed this issue 2026-08-08 09:01:36 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
timmy
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#283
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?