Not sure if I've configured something incorrectly, or if this behavior is documented but for some subset of repos I'm mirroring, I'm seeing a large number of duplicates being mirrored whose names end with what looks like a timestamp:
Furthermore, many (all but the latest/highest) look like this, even after hours/days:
Hope this is enough context - for the time being, I'm just running gitea-mirror periodically; otherwise, I'm getting hundreds more repos (almost 1k at this point) more repos being mirrored than intended.
But having said all that, this project is still awesome, thank you!
Not sure if I've configured something incorrectly, or if this behavior is documented but for some subset of repos I'm mirroring, I'm seeing a large number of duplicates being mirrored whose names end with what looks like a timestamp:
<img width="360" height="582" alt="Image" src="https://github.com/user-attachments/assets/6caaf5ea-c420-4d68-b28b-d0b541a841ec" />
Furthermore, many (all but the latest/highest) look like this, even after hours/days:
<img width="960" height="495" alt="Image" src="https://github.com/user-attachments/assets/54a438bc-e74b-4a61-bb30-96d0428442d7" />
Hope this is enough context - for the time being, I'm just running gitea-mirror periodically; otherwise, I'm getting hundreds more repos (almost 1k at this point) more repos being mirrored than intended.
But having said all that, this project is still awesome, thank you!
<!-- github-sync-id:3506509925 -->
@sunny-g this is weird and I have not seen this issue before is it with more than 1 repo or just this particular one ?
@sunny-g this is weird and I have not seen this issue before is it with more than 1 repo or just this particular one ?
<!-- github-comment-id:3393916362 -->
Furthermore, many (all but the latest/highest) look like this, even after hours/days:
Hope this is enough context - for the time being, I'm just running gitea-mirror periodically; otherwise, I'm getting hundreds more repos (almost 1k at this point) more repos being mirrored than intended.
But having said all that, this project is still awesome, thank you!
From what I know, some of the repos takes a lot longer to mirror than others, and sometimes it gets stuck because of timeout. I don't think that's necessary gitea-mirror's problem but more like github or gitea problems.
I actually wrote a bash script to mirror the repos and it does exactly the same thing. Also to note that there are repos out there just can't be mirrored. Don't ask me why. For example, https://github.com/MicrosoftDocs/azure-docs can't be mirrored. I have tried it so many ways, even through gitea itself (using New Migration).
> Furthermore, many (all but the latest/highest) look like this, even after hours/days:
>
> <img alt="Image" width="960" height="495" src="https://private-user-images.githubusercontent.com/2055636/500214053-54a438bc-e74b-4a61-bb30-96d0428442d7.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NjA3MTQ2MzIsIm5iZiI6MTc2MDcxNDMzMiwicGF0aCI6Ii8yMDU1NjM2LzUwMDIxNDA1My01NGE0MzhiYy1lNzRiLTRhNjEtYmIzMC05NmQwNDI4NDQyZDcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MTAxNyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTEwMTdUMTUxODUyWiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MWQyM2M0Nzc3OGI4MGJmMDA4MWRiYWJkZjMwYmJkODEwZmMzNjlkZTlkZWZiZWE3YzY4YzYwNjhkOTBiYzEyYSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.N5py6AjCNDHFMnnqstek8kb8x-3WF8JDWPb3UWfx96I">
> Hope this is enough context - for the time being, I'm just running gitea-mirror periodically; otherwise, I'm getting hundreds more repos (almost 1k at this point) more repos being mirrored than intended.
>
> But having said all that, this project is still awesome, thank you!
From what I know, some of the repos takes a lot longer to mirror than others, and sometimes it gets stuck because of timeout. I don't think that's necessary gitea-mirror's problem but more like github or gitea problems.
I actually wrote a bash script to mirror the repos and it does exactly the same thing. Also to note that there are repos out there just can't be mirrored. Don't ask me why. For example, https://github.com/MicrosoftDocs/azure-docs can't be mirrored. I have tried it so many ways, even through gitea itself (using New Migration).
<!-- github-comment-id:3416035926 -->
@Arrmm thanks for investigating deeper into it. Need to figure out why this maybe happening cause I don't remember changing anything drastic recently
@Arrmm thanks for investigating deeper into it. Need to figure out why this maybe happening cause I don't remember changing anything drastic recently
<!-- github-comment-id:3416435886 -->
I am still investigating. Give me another few days and I'll share the log so that we can all debug it together.
Can't say enough good things about this tool though. It is very pretty and easy to use.
I am still investigating. Give me another few days and I'll share the log so that we can all debug it together.
Can't say enough good things about this tool though. It is very pretty and easy to use.
<!-- github-comment-id:3416766266 -->
Can't say enough good things about this tool though. It is very pretty and easy to use.
@Arrmm Thank you. Next goal is to work towards ironing out all small annoying issues.
> Can't say enough good things about this tool though. It is very pretty and easy to use.
@Arrmm Thank you. Next goal is to work towards ironing out all small annoying issues.
<!-- github-comment-id:3417745621 -->
@sunny-g @Arrmm consider testing the image with the new PR for this #119 and see if it solves this issue. I would test it on a fresh gitea
@sunny-g @Arrmm consider testing the image with the new PR for this #119 and see if it solves this issue. I would test it on a fresh gitea
<!-- github-comment-id:3430338616 -->
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.
Not sure if I've configured something incorrectly, or if this behavior is documented but for some subset of repos I'm mirroring, I'm seeing a large number of duplicates being mirrored whose names end with what looks like a timestamp:
Furthermore, many (all but the latest/highest) look like this, even after hours/days:
Hope this is enough context - for the time being, I'm just running gitea-mirror periodically; otherwise, I'm getting hundreds more repos (almost 1k at this point) more repos being mirrored than intended.
But having said all that, this project is still awesome, thank you!
@sunny-g this is weird and I have not seen this issue before is it with more than 1 repo or just this particular one ?
I am also seeing this issue as well but typically it is 1 or 2 additional to the original.
@Arrmm can you add some related docker logs
From what I know, some of the repos takes a lot longer to mirror than others, and sometimes it gets stuck because of timeout. I don't think that's necessary gitea-mirror's problem but more like github or gitea problems.
I actually wrote a bash script to mirror the repos and it does exactly the same thing. Also to note that there are repos out there just can't be mirrored. Don't ask me why. For example, https://github.com/MicrosoftDocs/azure-docs can't be mirrored. I have tried it so many ways, even through gitea itself (using New Migration).
@Arrmm thanks for investigating deeper into it. Need to figure out why this maybe happening cause I don't remember changing anything drastic recently
I am still investigating. Give me another few days and I'll share the log so that we can all debug it together.
Can't say enough good things about this tool though. It is very pretty and easy to use.
@Arrmm Thank you. Next goal is to work towards ironing out all small annoying issues.
@sunny-g @Arrmm consider testing the image with the new PR for this #119 and see if it solves this issue. I would test it on a fresh gitea
This should be solved now @sunny-g @Arrmm feel free to reopen this issue if it persists