-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Neverending Repository Migration Blocks All Current and Future Migrations #17005
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Well, as it seems, there seems to exist an infinite recursion inside LDAP because of some error. (line Related: #12917 |
Yes, log coloring has been available since 1.7 - it's very helpful for looking at the logs on an color terminal or reader, but it can also easily be turned off as necessary However, the advice when sending us logs for issues, as linked to in the issue proforma (https://docs.gitea.io/en-us/logging-configuration/#debugging-problems) is to turn off the coloring unless you're able to strip out the coloring for us because Github (and Gitea for that matter, and most editors) won't apply the ANSI coloring codes so it's just going to make it harder for us to help.
Thank you for finding this - I'll take a look at that. Just on the face of it Clearly if it's a misconfiguration error we should be handling it and then inactivating the source. |
The only thing I have LDAP set up for is login to the Gitea instance, and I've never had any issue with it. I've just logged out and logged back in, and that works just fine. I'm also not using authentication (LDAP or other) in that migration of the Github repo that stalls forever; that migration is done with only a Github API token and no other credentials. Is there any way to just kill the migration? Maybe that will mitigate this issue. (Unfortunately stopping Gitea and restarting it doesn't help in that regard.) |
Yeah looking at the logs I don't think this is the issue. However, it's clear that the adminFilter and the restrictedFilter here are incorrect and you should check them.
I think we need to work out where in the migration it is stuck. The suspicious line to me is:
but I'm not sure if that's really the issue. When there is a migration you should now get told which thing it is attempting to migrate. What does it report that it is migrating? Could you add a trace logger with |
You also aren't telling us where you're migrating from. Is this from Github? |
Encountered the same issue on a fresh install. I've added a trace logger with
|
Please help, need a way to at least stop (fail) the migration somehow (restarting Gitea didn't help), so that I can push the same repo manually. |
It seems that you only have one worker for migration queue. 1.20 the queue has been completely rewritten, you can also set many workers (eg: 10) to work together, then the migration won't be blocked by a particular one. |
[x]
):The text was updated successfully, but these errors were encountered: