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?
<!-- github-comment-id:4020605854 -->
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.
> 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.
<!-- github-comment-id:4020697049 -->
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.
upgraded the docker image and now on booting it hangs, here's the logs.
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?
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.