-
Notifications
You must be signed in to change notification settings - Fork 176
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
HTTP 500 error code for repo query on gitee.com #191
Comments
If the api always return 500, we can't do anything besides contact gitee support. |
I raised this with gitee.com support now as well: https://gitee.com/oschina/git-osc/issues/IAA00L |
Stefan-Schmidt
added a commit
to eclipse-oniro-mirrors/mirror-sync
that referenced
this issue
Jul 5, 2024
Currently the gitee API to query the repos for an organization is retruning a HTTP 500 error. Switchign over to a static list for now until this is fixed. https://gitee.com/oschina/git-osc/issues/IAA00L Yikun/hub-mirror-action#191 Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Stefan-Schmidt
added a commit
to eclipse-oniro-mirrors/mirror-sync
that referenced
this issue
Jul 6, 2024
Currently the gitee API to query the repos for an organization is retruning a HTTP 500 error. Switchign over to a static list for now until this is fixed. https://gitee.com/oschina/git-osc/issues/IAA00L Yikun/hub-mirror-action#191 Signed-off-by: Stefan Schmidt <stefan.schmidt@huawei.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We are seeing an internal error with HTTP error code 500 for the gitee API query for organization repos:
This is happening in our OpenHarmony sync to GitHub:
https://github.com/eclipse-oniro-mirrors/mirror-sync/actions/runs/9696254218/job/26757783805#step:3:69
Curl is producing the same error. This is also true for other organizations I tested.
Is this API being removed from gitee or is it just broken at the moment? How do others work around this with hub-mirror-action?
We saw this first on June 1st. The same job worked without any changes on May 31th.
The text was updated successfully, but these errors were encountered: