Since updating to 3.14.o I think, I can no longer mirror anything, e.g. all my repos show up as failed:
In the journalctl logs, I honestly don't see to much, except a lot of spam from this:
Mar 25 11:11:20 gitea-mirror bun[44685]: Job 43da025b-46dd-4d77-82cf-0e2886f2d3ed has no log data
Which doesn't even make sense to me to even log this by default?
Thanks
Hi,
Since updating to 3.14.o I think, I can no longer mirror anything, e.g. all my repos show up as failed:
<img width="601" height="217" alt="Image" src="https://github.com/user-attachments/assets/8641e073-1894-42ed-9044-cfd5ad90fbfa" />
In the journalctl logs, I honestly don't see to much, except a lot of spam from this:
```bash
Mar 25 11:11:20 gitea-mirror bun[44685]: Job 43da025b-46dd-4d77-82cf-0e2886f2d3ed has no log data
```
Which doesn't even make sense to me to even log this by default?
Thanks
<!-- github-sync-id:4134251585 -->
@arunavo4 could you do a tagged release or pre-release with it? I can't pull a docker tag directly in proxmox helper scripts.
@arunavo4 could you do a tagged release or pre-release with it? I can't pull a docker tag directly in proxmox helper scripts.
<!-- github-comment-id:4140505940 -->
Failed to update mirror repository '/var/lib/forgejo/data/forgejo-repositories/crazywolf13-mirror/XXXXX.git': fatal: could not read Password for 'https://sanitized-credential@github.com': terminal prompts disabled
Also such errors are spammed in forgejo:
Failed to update mirror repository '/var/lib/forgejo/data/forgejo-repositories/crazywolf13-mirror/XXXXX.git': fatal: could not read Password for 'https://sanitized-credential@github.com': terminal prompts disabled
<!-- github-comment-id:4140655177 -->
Okay little update, I noticed all my repos are edited with some text that they are archived and gitea-mirror made a snapshot, yet those repos were all always available on github in the last days.
Together with removing the above setting, fully removing all repos that gitea-mirror touched and wrongfully edited and marked unavailable and re-syncing them through gitea-mirror it seems working now and all looks green in gitea-mirror.
<img width="838" height="351" alt="Image" src="https://github.com/user-attachments/assets/371ae05c-4ad7-461b-90b2-cea8b429007c" />
Okay little update, I noticed all my repos are edited with some text that they are archived and gitea-mirror made a snapshot, yet those repos were all always available on github in the last days.
Together with removing the above setting, fully removing all repos that gitea-mirror touched and wrongfully edited and marked unavailable and re-syncing them through gitea-mirror it seems working now and all looks green in gitea-mirror.
<!-- github-comment-id:4140830444 -->
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.
Hi,
Since updating to 3.14.o I think, I can no longer mirror anything, e.g. all my repos show up as failed:
In the journalctl logs, I honestly don't see to much, except a lot of spam from this:
Which doesn't even make sense to me to even log this by default?
Thanks
@CrazyWolf13 Try this
ghcr.io/raylabshq/gitea-mirror:pr-249Tho it seems to be working fine on my end.
@arunavo4 could you do a tagged release or pre-release with it? I can't pull a docker tag directly in proxmox helper scripts.
Also such errors are spammed in forgejo:
Failed to update mirror repository '/var/lib/forgejo/data/forgejo-repositories/crazywolf13-mirror/XXXXX.git': fatal: could not read Password for 'https://sanitized-credential@github.com': terminal prompts disabled
Okay little update, I noticed all my repos are edited with some text that they are archived and gitea-mirror made a snapshot, yet those repos were all always available on github in the last days.
Together with removing the above setting, fully removing all repos that gitea-mirror touched and wrongfully edited and marked unavailable and re-syncing them through gitea-mirror it seems working now and all looks green in gitea-mirror.