Fix capture settings recovery and stale status replies #15
Labels
No labels
status:done
status:in-progress
status:ready
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
rexlManu/garmith-app#15
Loading…
Add table
Add a link
Reference in a new issue
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?
Capture Settings currently keeps a failed status-read error after polling recovers. Concurrent action and polling reads can apply an older reply after newer state. Add focused tests, clear recovered read errors while preserving action errors, and ignore stale replies. Keep live verification and installed release update under #12 and #13.
Fixed and pushed:
63c4fa5. Three focused tests reproduced the failures before the fix; all five now pass. Successful reads clear recovered status errors while action errors remain visible. Read sequence numbers discard stale successes and failures. Typecheck, build, packaged capture/OCR/permissions and capture-settings checks pass.