feat(api): warm war status and statistics when DB is empty - #38
Merged
Conversation
DataCollector already runs collect_all_data in a background thread on startup; these GET handlers now fetch from the live scraper and persist when no row exists yet, so the first request can succeed before the initial collection finishes. Tests mock the scraper for 404 paths and cover live-fetch success. Made-with: Cursor
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.
When the database has no row yet,
GET /api/war/statusandGET /api/statisticsfetch from the live scraper, persist, and return the result so the first client request can succeed before the background initial collection fromDataCollector.start()finishes.Tests updated to mock scraper fallbacks and cover live-fetch success paths.
Made with Cursor