Repository navigation
fix: preserve cached calendars and report timeouts accurately - #89
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
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.
Slow responses were reported as offline, and cached calendars expired after seven days. Public service checks now wait up to 15 seconds, report timeouts separately, and keep cached calendars available when refreshes fail.
Version 1.5.20 requires docs 0.3.5 for offline search after restart and patches vulnerable development dependencies. Service-check JSON adds timedOut; failed public checks still return a nonzero exit code.
Validation: npm run check passes with 1,011 tests and zero audit findings. Built artifacts load 90-day-old event and school caches offline, and all public service checks pass.