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
```
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?
<!-- gh-comment-id:4020605854 -->
@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?
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.
<!-- gh-comment-id:4020697049 -->
@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.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
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.
@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 forimportedandfailedstatus 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?
@arunavo4 commented on GitHub (Mar 9, 2026):
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.