Make mobile Recent Work sync generation-safe and self-healing #1486

Merged
timmy merged 1 commits from timmy/1485-mobile-recent-work-sync into main 2026-08-27 21:55:40 +00:00
Owner

Summary

  • preserve operation generations so an older response cannot acknowledge a newer same-route Recent Work or pin update
  • overlay newer local state while the older response settles, then drain the newer generation
  • retry transient failures with bounded account-scoped exponential backoff

Tests

  • python3 -m pytest tests/test_mobile_recent_work.py tests/test_recent_work_store.py tests/test_recent_work_api.py -q (13 passed)
  • python3 -m pytest -q (2814 passed, 28 skipped)
  • node --check frontend/mobile-recent-work.js

Closes #1485

## Summary - preserve operation generations so an older response cannot acknowledge a newer same-route Recent Work or pin update - overlay newer local state while the older response settles, then drain the newer generation - retry transient failures with bounded account-scoped exponential backoff ## Tests - `python3 -m pytest tests/test_mobile_recent_work.py tests/test_recent_work_store.py tests/test_recent_work_api.py -q` (13 passed) - `python3 -m pytest -q` (2814 passed, 28 skipped) - `node --check frontend/mobile-recent-work.js` Closes #1485
timmy added 1 commit 2026-08-27 21:43:04 +00:00
fix: make mobile recent work sync generation-safe (Closes #1485)
All checks were successful
CI / lint (pull_request) Successful in 3m50s
CI / build-release (pull_request) Successful in 8s
CI / browser-journey (pull_request) Successful in 8m1s
CI / release-candidate (pull_request) Has been skipped
cec5b93665
timmy merged commit 5f9b5b3a7f into main 2026-08-27 21:55:40 +00:00
Sign in to join this conversation.
No reviewers
No Milestone
No project
No Assignees
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#1486
No description provided.