Merged
Conversation
yakanechi
approved these changes
Jan 16, 2026
minghay
previously approved these changes
Jan 20, 2026
Contributor
|
@yk634 You can consider making the loading more graphical by adding in style and changing the template text from |
minghay
approved these changes
Jan 21, 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
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.

Context
Currently, event search fetches all matching events at once.
In our environment, this can mean retrieving tens of thousands of records from the database, which may cause excessive load on both the API server and the UI.
In addition, when search results are rendered, the UI triggers one API request per displayed event to fetch its corresponding build status.
As more events become visible during scrolling, these requests are executed repeatedly.
If a user scrolls quickly (for example, dragging the scrollbar directly to the bottom), this behavior can result in a large number of build-status API calls being executed in a short period of time, leading to unnecessary load and potential performance degradation.
Objective
This PR introduces infinite scroll with pagination (10 items per page) for event search.
Instead of fetching all matching events at once, search results are loaded incrementally as the user scrolls.
This limits the number of events rendered at a time and reduces the number of per-event build-status API calls triggered during scrolling.
As a result:
References
License
I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.