[codex] fix stale Cloudflare calendar cache - #9
Merged
Merged
Conversation
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
1 participant
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
Fixes the Cloudflare-connected deployment path for the calendar Worker.
The repository is already connected in Cloudflare, so deploying from GitHub is not the missing step. The issue is that the Worker serves
CALENDAR_CACHEfirst. After a Cloudflare-connected deploy, KV can still contain an oldercalendar:body, causing subscribers to keep receiving stale calendar data until the monthly cron refresh runs.This change makes the Worker compare the bundled deploy-time calendar timestamp with the stored KV timestamp. If the bundled calendar is newer, the Worker serves the fresh bundled calendar immediately and refreshes KV in the background.
Validation
poetry run pytest -qpassed with 21 tests.npm run worker:verifypassed.