feat(lxlweb): make library fetching more robust; warm up caches on startup - #1650
Merged
Conversation
johanbissemattsson
approved these changes
Jul 30, 2026
johanbissemattsson
left a comment
Contributor
There was a problem hiding this comment.
LGTM!
A slightly more SvelteKit_ish_ way would be using an init hook but it should be no different than writing the initialisation logic at the top level of the module.
Member
Author
Good point! I adjusted it a bit. |
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.
Previously, if
startRefreshLibrariesfailed (for example, because the EMM API was unavailable), lxlweb would run with no library/org data for at least 12 hours (until a regularly scheduled refresh succeeded).This PR does a couple things:
refreshLibrariesfails, it keeps trying every 30 seconds instead of waiting for 12 hours. Only after a successful fetch does it schedule the 12-hour refresh interval.Related to #1649