Migration gets stuck and/or fails #603
Both Gitea instances, both v1.16.5.
The process has been going on for a couple of hours now, stating
When visiting the repo in a logged out state instead Codeberg says
Migrating from https://git.minetest.land/MineClone2/MineClone2 failed.
I'm able to clone what I think is the full repo to my local machine. I'm able to see some repo issues (54 Open, 46 Closed) from the https://codeberg.org/issues view but far from all (539 Open, 1234 Closed). From the former server's logs I can tell that Codeberg is still rapidly hitting the API for content, yet the list of issues on https://codeberg.org/issues doesn't grow.
Should I stand by for some more hours or has it failed? What do I do?
Hmm, I suppose if the migration really failed, there is no point in waiting.
But maybe someone else like @6543 can have a look?
oh awesome minetest plugins comming to codeberg 🎉
yes sure will look into
will need more investigation ...
Any news? The old server went bust because of the 25GB log file the migrationen generated, but it's up again.
bare git works, wiki works, ... labels, milestone, releases also
ok so the issue si within
pull migration - but I did not got any stactrace back jet
Thanks! 🙌 I remember when migrating the issues off Github the migration failed until I edited out all unicode emojis out of the issues. I also get Error 500 on my instance whenever trying to post emojis, if that helps. To be clear, there shouldn't be any emojis in the issues being migrated, and Codeberg seems to handle unicode emojis well regardless. 🤷
Hmm. I tried to migrate repos from https://gitlab.com/interpeer/ and they failed as well. Unfortunately, there's not much to go by other than a message that the migration failed.
@tacotexmex I guess you have wrong settings in your db -> https://docs.gitea.io/en-us/faq/#why-are-emoji-broken-on-mysql
@jfinkhaeuser I think this was because of enabled wikis that where not initilized on gitlab side - it should be fixed
Yes, for me it's fixed @6543 - can't speak about others.
well I fixed some migration bugs - but the bug causing this issue HERE is not
Are there any other routes for imports to Codeberg. I'm root on the server I'm trying to migrate from and wouldn't mind importing the whole instance, users and all. That would actually be really great…
at gitea we work on a dump & offline migration feature ...
but that is in active dev (need time) ...
the pure git data you always can pull & push ... but it's about the issues etc ...
... your insance do have 428 public users - I think it's more fesable if they just create an acount here
... I would migrate step by step (first with smal repos - they should work out...)
... for the mentioned big repo we either have to try to manually dump and import or sort out the current issue
i tried to migrate my repos from github, but most of them get stuck, although they are tiny. example:
Seems like it did get migrated, https://codeberg.org/jschwender/FY6600-15-30-50-60M. It might take a lot longer to migrate than usual.
No due date set.
No dependencies set.
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?