Remove pulling google events from Google if we already have a watch / notification channel open
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Refactor
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- google-cloud, python
- Domain
- api, backend, performance
Research direction
Start by reviewing pull request 1529 and the linked Google Calendar push-notification documentation, then trace the existing path that pulls remote Google Calendar events and checks notification-channel state. Done means calendars with an open channel use the database data without pulling remote events, while calendars without one retain the existing behavior.
Written by the indexing model from the issue text.
Description
After https://github.com/thunderbird/appointment/pull/1529 gets merged in, we will have watch / notification channels open which receive webhook calls when events gets changed remotely on the Subscriber's Google Calendar.
Assuming that our DB data is correct and up-to-date, we can have a huge performance boost by not having to pull remove events if we already have a channel open for that calendar.
Paraphrasing @MelissaAutumn here:
Could you additionally cut a ticket to remove pulling the google events from Google's end if they have a watch channel open? Because then we can just pull from our db and assume the db is up-to-date. It's a bit out of scope here but would be a huge perf boost.
Ref: https://github.com/thunderbird/appointment/pull/1529#pullrequestreview-4032158837
- Dominant language
- Python
- Stars
- 552
- Forks
- 29
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from thunderbird/appointment
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
thunderbird/appointment#1735 · 3 comments ·
-
thunderbird/appointment#1840 · 1 assignee ·
-
thunderbird/appointment#1836 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
thunderbird/appointment#1831 ·
-
zendesk
Difficulty 3/5 1-2 days Newbie friendliness 52/100
thunderbird/appointment#1819 ·
All issues in thunderbird/appointment
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
bancolombia/sentinel#23 ·
-
test md OpenCI
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
langchain-ai/deepagents#6450 ·
-
bug client
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100