-
-
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
Refactor Find Sources and fix bug when view a user who belongs to an unactive auth source #27798
Conversation
…unactive auth source
…ea into lunny/fix_unactive_auth_source
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are some changes to these functions in #25165 to make them more generic. Could you utilize some of these update function names/args to make conflict merging easier?
I think the changes are the correct direction. I will help to resolve your PR's conflict after this merge. |
I was unable to create a backport for 1.20. @lunny, please send one manually. 🍵
|
I was unable to create a backport for 1.21. @lunny, please send one manually. 🍵
|
There are too many conflicts, so I think maybe it's not necessary to backport to v1.21 and v1.20. |
* upstream/main: Refactor Find Sources and fix bug when view a user who belongs to an unactive auth source (go-gitea#27798) [skip ci] Updated translations via Crowdin Add `Hide/Show all checks` button to commit status check (go-gitea#26284) Fix http protocol auth (go-gitea#27875) Display issue task list on project cards (go-gitea#27865) Reduce margin/padding on flex-list items and divider (go-gitea#27872)
…unactive auth source (go-gitea#27798) The steps to reproduce it. First, create a new oauth2 source. Then, a user login with this oauth2 source. Disable the oauth2 source. Visit users -> settings -> security, 500 will be displayed. This is because this page only load active Oauth2 sources but not all Oauth2 sources.
Now that we have go-gitea#27798 we don't need the check from go-gitea#27870 anymore. With the check it's not possible to remove an inactive auth source from the user.
Continue of go-gitea#27798 and move more functions to `db.Find` and `db.Count`.
The steps to reproduce it.
First, create a new oauth2 source.
Then, a user login with this oauth2 source.
Disable the oauth2 source.
Visit users -> settings -> security, 500 will be displayed.
This is because this page only load active Oauth2 sources but not all Oauth2 sources.