-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix issue #6060: Speed up loading of GitHub repositories in the front-end hero page #6062
base: main
Are you sure you want to change the base?
Conversation
@openhands-agent This PR is failing frontend unit tests and linting. Please examine the github workflows for linting/testing the frontend, run the workflows, and fix any errors. |
…s in the front-end hero page
Status: UNRESOLVED ❌ Summary:
Required Actions:
Recommendation: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This won't really speed up loading since the maximum value for the per_page
query param is capped at 100 (https://docs.github.com/en/rest/apps/installations?apiVersion=2022-11-28#list-repositories-accessible-to-the-app-installation)
The number of results per page (max 100).
What I was planning to do was implement proper listeners on the drop down (e.g., onEndReached
) and call the next set of repos there rather than fetch them all at once.
The problem is NextUI autocomplete makes it very hard to extend it that way, so I was going to create a custom one (eventually)
End-user friendly description of the problem this fixes or functionality that this introduces
Speed up loading of GitHub repositories in the front-end hero page
Give a summary of what the PR does, explaining any non-trivial design decisions
This PR increases the pagination of repo requests in the frontend to download 1000 entries, which will speed up loading.
Note that this pulls in the removal of open-cv from #6064, which was necessary to get it to run on my machine.
Link of any specific issues this addresses
Fixes #6060
To run this PR locally, use the following command: