-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
GetCommitStatuses API errors when requesting the second page #28764
Comments
Merged
lunny
pushed a commit
that referenced
this issue
Jan 15, 2024
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Jan 15, 2024
fuxiaohei
pushed a commit
to fuxiaohei/gitea
that referenced
this issue
Jan 17, 2024
henrygoodman
pushed a commit
to henrygoodman/gitea
that referenced
this issue
Jan 31, 2024
silverwind
pushed a commit
to silverwind/gitea
that referenced
this issue
Feb 20, 2024
Automatically locked because of our CONTRIBUTING guidelines |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I am running renovate on my self hosted gitea instance and it fails to get the statuses of a commit if the commit has more statuses than the default limit (requiring renovate to request a second page).
Here are what I believe to be the relevant logs (first group is the successful first request, second group is the failure):
It looks like the SQL command is applying the OFFSET of the page to the final count rather than the actual query.
gitea/models/git/commit_status.go
Lines 237 to 239 in 669bbba
The renovate error message (which I don't think is necessary, as I believe it is doing what it should) is:
Gitea Version
1.21.3
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
2.43.0
Operating System
Linux Ubuntu 23.10
How are you running Gitea?
Official binary
Database
SQLite
The text was updated successfully, but these errors were encountered: