Migration of repos from Github stuck at in progress sometimes rendering the repo unusable #300

Closed
opened 1 year ago by arghyadeep · 17 comments

When migrating a repo from Github to Codeberg, it gets stuck at times in In-Progress status.

See this: https://codeberg.org/arghyadeep/opencv4js-stuckmigration

This makes the repo completely unusable and it's not possible to kill the process or delete the repo and redo it. The repo name is also stuck and cannot be reused.

When migrating a repo from Github to Codeberg, it gets stuck at times in In-Progress status. See this: https://codeberg.org/arghyadeep/opencv4js-stuckmigration This makes the repo completely unusable and it's not possible to kill the process or delete the repo and redo it. The repo name is also stuck and cannot be reused.
hw commented 1 year ago
Owner

renamed to arghyadeep/opencv4js-stuckmigration for investigation

renamed to `arghyadeep/opencv4js-stuckmigration` for investigation
hw added the
gitea-related
bug
labels 1 year ago
6543 commented 1 year ago
Collaborator

@arghyadeep you can delete/cancle migration with "Delete Repo" on https://codeberg.org/arghyadeep/opencv4js-stuckmigration/settings

@arghyadeep you can delete/cancle migration with "Delete Repo" on https://codeberg.org/arghyadeep/opencv4js-stuckmigration/settings
hw commented 1 year ago
Owner

@lhinderberger : would it make sense to add a troubleshooting-section to the docs explaining the why-and-how-to-resolve?

@lhinderberger : would it make sense to add a troubleshooting-section to the docs explaining the why-and-how-to-resolve?

@hw - Not too sure - was this a mistake that's user-resolvable or did it turn out to be a bug?

@hw - Not too sure - was this a mistake that's user-resolvable or did it turn out to be a bug?
Poster

@lhinderberger - As per my understanding, it's an issue with Github API throttling the process.

@lhinderberger - As per my understanding, it's an issue with Github API throttling the process.

In that case, I'd say it's better to add a note on the migration progress screen to indicate that things could take a while due to other services throttling their API.

Another idea could be to make the migration progress screen a bit more detailed.

In that case, I'd say it's better to add a note on the migration progress screen to indicate that things could take a while due to other services throttling their API. Another idea could be to make the migration progress screen a bit more detailed.
6543 commented 1 year ago
Collaborator

@arghyadeep what was the url - so I can test migration localy

@arghyadeep what was the url - so I can test migration localy
Poster

Github URL: https://github.com/arghyadeep-k/opencv4js

Please note that it’s not dependant on this repo. I tried the migration again later and it completed within seconds.

Github URL: https://github.com/arghyadeep-k/opencv4js Please note that it’s not dependant on this repo. I tried the migration again later and it completed within seconds.

Another stuck migration is: https://codeberg.org/NoNamePro0/vlang
Original Repo: https://github.com/vlang/v

Another stuck migration is: https://codeberg.org/NoNamePro0/vlang Original Repo: https://github.com/vlang/v
hw commented 1 year ago
Owner

thank you for reporting! Did the migration into a second repo succeed for you?

thank you for reporting! Did the migration into a second repo succeed for you?

Yeah! Now it looks good! Thanks!

Yeah! Now it looks good! Thanks!
hw commented 1 year ago
Owner

@arghyadeep you can delete/cancle migration with "Delete Repo" on https://codeberg.org/arghyadeep/opencv4js-stuckmigration/settings

Deleted as currently a number of gitea PRs resolve migration issues.

> @arghyadeep you can delete/cancle migration with "Delete Repo" on https://codeberg.org/arghyadeep/opencv4js-stuckmigration/settings Deleted as currently a number of gitea PRs resolve migration issues.
6543 commented 1 year ago
Collaborator

@hw wile it wont go in at this state ... (It do not cancle migration rather than just delete repo-files and bring migration to calcle because it fails of missing files)

https://github.com/go-gitea/gitea/pull/12917 could be a nice patch for Codeberg

It does the exact same thing as if someone goes to /settings page and delete a repo witch is in migration loop

@hw wile it wont go in at this state ... (It do not cancle migration rather than just delete repo-files and bring migration to calcle because it fails of missing files) <https://github.com/go-gitea/gitea/pull/12917> could be a nice patch for Codeberg It does the exact same thing as if someone goes to /settings page and delete a repo witch is in migration loop
hw commented 1 year ago
Owner

Very useful.

Very useful.
6543 commented 1 year ago
Collaborator

12917 is not quite ready, but admins now are able to see migration tasks and cancle them if needed: https://github.com/go-gitea/gitea/pull/13792

12917 is not quite ready, but admins now are able to see migration tasks and cancle them if needed: https://github.com/go-gitea/gitea/pull/13792
hw commented 1 year ago
Owner

This is a cool feature.

This is a cool feature.
Collaborator

Does this still happen often? If it just takes it's time, then this issue can be closed? Also with the recently increased timeouts?

Does this still happen often? If it just takes it's time, then this issue can be closed? Also with the recently increased timeouts?
rwa closed this issue 7 days ago
Sign in to join this conversation.
No Milestone
No Assignees
6 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.