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

Open
opened 2 weeks ago by arghyadeep · 11 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 2 weeks ago
Owner

renamed to arghyadeep/opencv4js-stuckmigration for investigation

renamed to `arghyadeep/opencv4js-stuckmigration` for investigation
hw added the
gitea-related issue
label 2 weeks ago
hw added the
bug
label 2 weeks ago
6543 commented 2 weeks 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 2 weeks 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?
lhinderberger commented 2 weeks ago
Collaborator

@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?
arghyadeep commented 2 weeks ago
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.
lhinderberger commented 2 weeks ago
Collaborator

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 2 weeks ago
Collaborator

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

@arghyadeep what was the url - so I can test migration localy
arghyadeep commented 2 weeks ago
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 2 weeks 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!
Sign in to join this conversation.
No Milestone
No Assignees
5 Participants
Notifications
Due Date

No due date set.

Dependencies

This issue currently doesn't have any dependencies.

Loading…
There is no content yet.