Fix Google Calendar task sync reliability and rendering#1851
Open
martin-forge wants to merge 1 commit intocallumalpass:mainfrom
Open
Fix Google Calendar task sync reliability and rendering#1851martin-forge wants to merge 1 commit intocallumalpass:mainfrom
martin-forge wants to merge 1 commit intocallumalpass:mainfrom
Conversation
This was referenced Apr 30, 2026
568314a to
ca81b1e
Compare
ca81b1e to
5ff79ac
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This combines the Google Calendar fixes from #1802, #1832, #1843, and #1844 into one PR. I think they are easier to review together because they touch the same sync path and share metadata assumptions.
Maintainer note
I opened this as a combined PR because these fixes all sit in the Google Calendar task sync path, and the later reliability fixes depend on the recurring-exception metadata from #1802. One merge should be simpler than sequencing four branches.
Validation
npm test -- tests/services/TaskCalendarSyncService.test.ts tests/unit/issues/issue-google-calendar-delete-retry-queue.test.ts tests/unit/issues/issue-google-calendar-duplicate-investigation.test.ts tests/unit/issues/issue-google-calendar-archive-reliability.test.ts tests/unit/issues/issue-1696-gcal-recurring-reschedule.test.ts tests/unit/issues/issue-1696-local-calendar-recurring-reschedule.test.ts tests/unit/issues/issue-1823-zero-duration-google-calendar-list-duplication.test.ts --runInBandnpm run typechecknpm run build:testTZ=UTC npm test -- --runInBand --silentNote: a non-UTC local full test run still has two pre-existing timezone-sensitive failures in
due-date-timezone-inconsistency.test.tsandissue-327-failing-test.test.ts; the UTC run passes.