[GH-ISSUE #219] Startup appears to hang during repository status repair #228

New Issue

GiteaMirror · 2026-04-11T09:10:46-05:00

GiteaMirror commented

2026-04-11 09:10:46 -05:00

Originally created by @kapdon on GitHub (Mar 9, 2026).
Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/219

upgraded the docker image and now on booting it hangs, here's the logs.

Setting application version: 3.12.5
Checking for environment configuration...
No GitHub/Gitea environment variables found, skipping env config initialization.
✅ Environment configuration loaded successfully
Running startup recovery...
Running startup recovery using compiled script...
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully
=== Gitea Mirror Startup Recovery ===
Timeout: 30000ms
Force recovery: false
Checking if recovery is needed...
✅ No jobs need recovery. Startup can proceed.
✅ Startup recovery completed successfully
Running repository status repair...
Running repository repair using compiled script...
Successfully connected to SQLite database using Bun's native driver
🔄 Checking for pending migrations...
✅ Database migrations completed successfully

Originally created by @kapdon on GitHub (Mar 9, 2026). Original GitHub issue: https://github.com/RayLabsHQ/gitea-mirror/issues/219 upgraded the docker image and now on booting it hangs, here's the logs. ``` Setting application version: 3.12.5 Checking for environment configuration... No GitHub/Gitea environment variables found, skipping env config initialization. ✅ Environment configuration loaded successfully Running startup recovery... Running startup recovery using compiled script... Successfully connected to SQLite database using Bun's native driver 🔄 Checking for pending migrations... ✅ Database migrations completed successfully === Gitea Mirror Startup Recovery === Timeout: 30000ms Force recovery: false Checking if recovery is needed... ✅ No jobs need recovery. Startup can proceed. ✅ Startup recovery completed successfully Running repository status repair... Running repository repair using compiled script... Successfully connected to SQLite database using Bun's native driver 🔄 Checking for pending migrations... ✅ Database migrations completed successfully ```

GiteaMirror closed this issue

2026-04-11 09:10:46 -05:00

GiteaMirror commented

2026-04-11 09:10:47 -05:00

@kapdon commented on GitHub (Mar 9, 2026):

ah ok I actually know what happened here after looking at repair-mirrored-repos.js, since the recovery script checks for imported and failed status it's attempting to check and validate all repos, I've imported a lot 😅 almost 2k repos. gitea was responding slowly so it was just hanging.

maybe increase verbosity here when repair script can't seem to reach gitea?

@kapdon commented on GitHub (Mar 9, 2026): ah ok I actually know what happened here after looking at `repair-mirrored-repos.js`, since the recovery script checks for `imported` and `failed` status it's attempting to check and validate all repos, I've imported a lot 😅 almost 2k repos. gitea was responding slowly so it was just hanging. maybe increase verbosity here when repair script can't seem to reach gitea?

GiteaMirror commented

2026-04-11 09:10:48 -05:00

@arunavo4 commented on GitHub (Mar 9, 2026):

ah ok I actually know what happened here after looking at repair-mirrored-repos.js, since the recovery script checks for imported and failed status it's attempting to check and validate all repos, I've imported a lot 😅 almost 2k repos. gitea was responding slowly so it was just hanging.

maybe increase verbosity here when repair script can't seem to reach gitea?

Will check what else we can surface, don't wanna dump too much info in the logs. Let me see how can we add info when Gitea is slow to respond. Thank you for reporting this.

@arunavo4 commented on GitHub (Mar 9, 2026): > ah ok I actually know what happened here after looking at `repair-mirrored-repos.js`, since the recovery script checks for `imported` and `failed` status it's attempting to check and validate all repos, I've imported a lot 😅 almost 2k repos. gitea was responding slowly so it was just hanging. > > maybe increase verbosity here when repair script can't seem to reach gitea? Will check what else we can surface, don't wanna dump too much info in the logs. Let me see how can we add info when Gitea is slow to respond. Thank you for reporting this.