| Commit message (Collapse) | Author | Age | Files | Lines | |
|---|---|---|---|---|---|
| * | fix(test): stop the syncing-p tests leaking in-flight state | Craig Jennings | 4 days | 1 | -43/+73 |
| | | | | | | | | | | | | | | - They cleared the module's state hash on entry, not on exit. - One marks "proton" syncing to exercise the dispatcher's in-flight guard. - A sibling dispatch test uses a calendar also named "proton". - ERT runs them in that order, so the dispatch became a no-op and it failed. - Now each test let-binds a private hash, matching the sibling test files. - Added a test that pins the isolation itself. The failure was invisible from both directions. make test runs each file in its own Emacs, and the editor hook skipped this family for exceeding its file cap. It only appears when the 63 calendar-sync files run in one process. | ||||
| * | fix(calendar-sync): skip overlapping syncs for the same calendar | Craig Jennings | 2026-06-30 | 1 | -0/+84 |
| A timer tick that fired while a calendar's previous fetch was still running launched a second concurrent sync for that calendar, wasting work and racing to write the same org file. The dispatcher now skips a calendar whose status is already syncing and logs the skipped tick. The sentinel resets the status on process exit, so the skip clears on its own. load-state also clears a stale syncing status left by a crash, so a calendar can't be skipped forever. | |||||
 |
git.cjennings.net : dotemacs | |
| My Emacs configuration | Craig Jennings |
| aboutsummaryrefslogtreecommitdiff |