-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
500 Internal Server Error when creating new pull request #1696
Comments
possibly related to #1372 |
Setting this should make the logs waaaay more verbose 🙂 [log]
LEVEL=Trace |
As a side note I also get 500 back when closing an already existing pull request. |
Some additional information. It seems I can reproduce this by just closing/re-opening a PR. When creating a new PR it always fails (for the repository in question). But when re-opening/closing it fails randomly, i.e. fails sometimes and succeeds sometimes. The pattern I can see when I get 500 back seems to be related to the database, i.e. See summary below: Create a new PRThis always fails (for the repository in question):
Re-opening a closed PRSometimes fails, sometimes not. Seems it works/fails every other time I re-open a PR. When re-opening fails:
When re-opening succeeds:
When closing a PRWhen closing fails:
When closing succeeds:
|
Some more information. If after I have received a 500 and refresh the page, it always works. So seems to me that we sometimes abort with 500 before returning the pr-page. This makes sense too since creating/closing/re-opening is something more than just doing a simple http GET on the page. |
Duplicate of #1434 |
[x]
):Description
The 500 internal server error only shows up on some repositories. I have tried on both
try.gitea.io
and on our self hosted gitea and PRs work just fine on a brand new small repo (like two tiny text files). However on some repositories it seems we always get 500 back.Unfortunately there's no other information than the
500 Internal Server Error
message in the log. Can I enable more verbose logging somehow or are there other logs to dig from? This is trivial for me to reproduce in our environment so should be easy for me to get to the bottom if I get some assistance in digging :)The text was updated successfully, but these errors were encountered: