Skip to content

frontend: recover comment queues blocked by an old session write #3362

Description

@Chris0Jeky

A same-comment PATCH/DELETE queue in #3360 is keyed by card/comment ID across session resets. If an old transport never settles, a replacement session editing the same comment waits behind that predecessor and retains its own loading token. This is a MEDIUM availability concern, distinct from stale cache/session publication and the confirmed queued-intent navigation fix.

Acceptance:

  • Define explicit recovery for a new-session same-comment operation blocked behind an unresolved old transport.
  • Preserve user intent ordering and distinguish an unanswered write from a write known not to have reached the server; aborting transport does not undo a committed write.
  • Do not simply clear or bypass tails if that can allow old and new writes to commit in reverse order.
  • Deferred real-Pinia tests cover recovery, truthful loading, and suppression of old-session cache/error publication.

Related stalled-column policy: #3357. Source review: #3360 (comment). Classified once as a nonblocking follow-up; not a request to reopen the completed source #3304 review cycle.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Priority IIIValuable but unscheduled: residuals, tech-debt, performance, depth work.bugSomething isn't workingfrontendPrimary implementation impact in Vue/TypeScript UI and client runtime.

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions