Conversation
Context: Large job histories make the asset status page slow or time out. Change: Add opt-in job pagination, batch Redis retrieval, and cache status-page job lists for one minute.
Context: Job histories now use Redis batching and page-scoped enrichment. Change: Verify legacy and paged responses, cache reuse, expiry, and invalidation.
Context: API clients and status-page users need the pagination and freshness contract. Change: Document optional paging, response counts, and the one-minute cache window.
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Documentation build overview
13 files changed ·
|
Context: CI exposed a cached job whose Redis record had been cleared between tests. Change: Read the status loaded with the cached job rather than refreshing it from Redis.
Context: A CI test failed when a cached RQ job refreshed its missing Redis status. Change: Verify job enrichment uses the cached status throughout the cache window.
Context: The status page lost Created At and Queue ordering when it moved to server-side pagination. Change: Add only the query fields the endpoint uses, sort before page selection, restore table controls, and clarify cache eviction.
Context: The status table now orders Created At and Queue across all pages. Change: Cover both queue directions and ascending enqueue time in the asset jobs API.
Context: The status table can order jobs by Created At and Queue across pages. Change: Document the sort-by and sort-dir API parameters.
Context: The status cache duration and capacity were embedded in get calls and eviction logic. Change: Define both limits on JobCache and let the status page opt into caching with a boolean.
Context: The cache lifetime now belongs to JobCache. Change: Exercise expiry and invalidation through the explicit cache opt-in.
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
Signed-off-by: Nicolas Höning <nicolas@seita.nl>
This branch has not been deployed
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.
Description
Closes #2617
documentation/changelog.rstThe long loading time probably stems from JSON manufacturing, but we also don't want to re-read all jobs from Redis on each page iteration (the order is also not always the same)
Look & Feel