Fix: change frontend cache time#1889
Open
MarceloRobert wants to merge 1 commit intokernelci:mainfrom
Open
Conversation
Also removes eslint rule ignore
MarceloRobert
added
the
Frontend
gustavobtflores
approved these changes
May 5, 2026
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
3 participants
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.
The frontend query cache can stale some requests, which in turn can show outdated numbers between treeListing, treeDetails and treeCommitHistory. Lowering the cache time will technically increase the number of requests, but this can be done without much concern since we have improved endpoint performance. Besides, without this risk for outdated numbers there is less chance for confusion in users when they see trees that are receiving data in real time.
Changes
Also removes eslint rule ignore
How to test
Go to any frontend page, check that if you make the same request within 30s it will get the data from cache (it won't perform the request again) and after 30s it will redo the request.