fix-github-discover-progress
π Bug Fixesβ
GitHub connection test timing out on large organizationsβ
Goal: Test connection listed hundreds of repositories and then failed at 10 seconds, before the backend finished paging the organization.
Solution: After the first page, the remaining pages are requested together, five at a time, and never past the last page GitHub reports. Personal and collaborator repos stay on GET /user/repos; organization repos are not downloaded a second time. The connection test streams progress (Listing repositories⦠600) with the number of repositories received so far, and no total. The client waits up to 60 seconds for that listing.
Files Modified:
src/protocol/source/github/github.service.ts- fetch remaining pages in parallel and report a running countsrc/protocol/source/github/github.service.spec.ts- cover the last-page limit and the running countsrc/protocol/source/source.service.ts- forward listing progress for GitHubsrc/app.controller.ts- stream discover progress to the connection testui/src/protocol/tower.api.ts- read the GitHub discover stream and wait up to 60 secondsui/src/pages/workflows/stepForms/StepInitForm.tsx- show how many repositories have arriveddocs/user/configuration/sources.md- describe the running count during Test connectiondocs/user/fr/configuration/sources.md- same note in French