-
-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
Internal Server Error accessing my profile on try.gitea.io #20002
Comments
Looking at the logs it appears that this is related to GetActiveStopwatch
#20008 should fix this. |
Still happens as of 1.17.0+dev-738-gea9997a9d |
The fixing commit is: v1.17.0-dev-741-gae446b13f so 1.17.0+dev-738-gea9997a9d is 3 commits before the fix was committed and shouldn't be expected to have the fix. |
I also have 500 error when authorizing but could be different, probably related to 2FA |
I'd need to know when you tried to do this so we could check the logs. |
Closed as I cannot reproduce it in the try site now. Fell free to reopen it if it occurs again. |
Description
If I go to https://try.gitea.io/strk, logging in via github OAuth, I get a 500
Gitea Version
Gitea Version: 1.17.0+dev-736-g719eb4a87
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
Only on try.gitea.io
Database
No response
The text was updated successfully, but these errors were encountered: