Large number of forks causes long page load times
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 64/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- graphql, typescript
- Domain
- frontend, performance
Research direction
Read src/bot/graphql.ts around getReposInOrgGQL and src/hooks/useForks.tsx around useForksData, then reproduce the delay with an organization containing many mirrors while recording network logs. Identify why the paginated UI waits on multiple fork-detail queries; done means the fork list displays without waiting for all details and the request time is reduced.
Written by the indexing model from the issue text.
Description
Describe the bug
When using the private mirrors UI to view the list of forks for an organization that contains a large number of forks the page can take a long time to initially load despite the use of pagination.
To Reproduce
- Open the private-mirrors UI
- Open the browser developer console to ensure that network logs are being captured
- Navigate to an organization that contains a lot of mirrors (in testing 150 repositories cause the load to take about 30 seconds)
- Look through the network logs and add up the time that it takes for all of the "getReposInOrgGQL" queries to run
Expected behavior
The private-mirrors UI should effectively paginate and lazy load the fork list to avoid making the user wait for all fork details to load before displaying any of them. The "getReposInOrgGQL" query and useForksData function should also be investigated to determine if other optimizations can and should be made.
Screenshots
No response
Additional context
No response
- Dominant language
- TypeScript
- Stars
- 203
- Forks
- 42
- Avg merge
- 1h 15m
- Merged PRs (30d)
- 8
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from github-community-projects/private-mirrors
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
github-community-projects/private-mirrors#525 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
github-community-projects/private-mirrors#524 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-2 days Newbie friendliness 68/100
github-community-projects/private-mirrors#449 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 45/100
github-community-projects/private-mirrors#485 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 48/100
github-community-projects/private-mirrors#481 ·
Maintainers usually reply within 1 day
All issues in github-community-projects/private-mirrors
Similar issues
-
no-repo-link tool-submission
Difficulty 1/5 Under an hour Newbie friendliness 66/100
BraveOPotato/NoSignups#2458 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
drmrd/vernacular#1061 ·
Maintainers usually reply within 1 day
-
[Bug] PUT /profiles/{id} silently drops design_prompt — designed voice profiles cannot be editedOpen
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
automated issue report
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
eventua11y/eventua11y.com#982 ·
Maintainers usually reply within 1 day