Skip to content
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

Closed
strk opened this issue Jun 17, 2022 · 7 comments
Closed

Internal Server Error accessing my profile on try.gitea.io #20002

strk opened this issue Jun 17, 2022 · 7 comments
Labels

Comments

@strk
Copy link
Member

strk commented Jun 17, 2022

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

@strk strk added the type/bug label Jun 17, 2022
@zeripath
Copy link
Contributor

zeripath commented Jun 17, 2022

Looking at the logs it appears that this is related to GetActiveStopwatch

router.log:2022/06/17 17:59:08 [62acc0ec] router: completed GET /strk for 172.18.0.3:38034, 500 Internal Server Error in 3.2ms @ repo/issue_stopwatch.go:81(repo.GetActiveStopwatch)

#20008 should fix this.

@strk
Copy link
Member Author

strk commented Jun 17, 2022

Still happens as of 1.17.0+dev-738-gea9997a9d

@strk
Copy link
Member Author

strk commented Jun 17, 2022

Screenshot_20220618-003103

@zeripath
Copy link
Contributor

zeripath commented Jun 17, 2022

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.

@lafriks
Copy link
Member

lafriks commented Jun 18, 2022

I also have 500 error when authorizing but could be different, probably related to 2FA

@zeripath
Copy link
Contributor

I'd need to know when you tried to do this so we could check the logs.

@lunny
Copy link
Member

lunny commented Mar 8, 2023

Closed as I cannot reproduce it in the try site now. Fell free to reopen it if it occurs again.

@lunny lunny closed this as completed Mar 8, 2023
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

4 participants