-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
500 error on pulls page (related to dismissed review comment) #27306
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
Labels
Comments
How to reproduce ? |
As the PR page gives a HTTP 500 I cannot easily see which actions happened in the history of this PR. |
lunny
added a commit
that referenced
this issue
Sep 29, 2023
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Sep 29, 2023
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Sep 29, 2023
lunny
added a commit
that referenced
this issue
Sep 29, 2023
Backport #27326 by @lunny Fix #27306 Co-authored-by: Lunny Xiao <[email protected]>
lunny
added a commit
that referenced
this issue
Sep 29, 2023
Backport #27326 by @lunny Fix #27306 Co-authored-by: Lunny Xiao <[email protected]>
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
…#27344) Backport go-gitea#27326 by @lunny Fix go-gitea#27306 Co-authored-by: Lunny Xiao <[email protected]> (cherry picked from commit b6b71c7)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
I'm not sure exactly sure what caused this, but we are getting a HTTP 500 error on a certain pull request.
It has something to do with dismissed reviews, I believe comment.Review is nil here:
gitea/models/issues/comment_list.go
Lines 459 to 460 in e502be4
Gitea Version
1.20.4
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
docker
Database
PostgreSQL
The text was updated successfully, but these errors were encountered: