-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Fix login error when user has an unsupported visibility type #23496
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
Closed
Closed
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -346,25 +346,26 @@ func TestUpdateUser(t *testing.T) { | |
user := unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2}) | ||
|
||
user.KeepActivityPrivate = true | ||
assert.NoError(t, user_model.UpdateUser(db.DefaultContext, user, false)) | ||
assert.NoError(t, user_model.UpdateUser(db.DefaultContext, user, false, false)) | ||
user = unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2}) | ||
assert.True(t, user.KeepActivityPrivate) | ||
|
||
setting.Service.AllowedUserVisibilityModesSlice = []bool{true, false, false} | ||
user.KeepActivityPrivate = false | ||
visibilityChanged := user.Visibility != structs.VisibleTypePrivate | ||
user.Visibility = structs.VisibleTypePrivate | ||
assert.Error(t, user_model.UpdateUser(db.DefaultContext, user, false)) | ||
assert.Error(t, user_model.UpdateUser(db.DefaultContext, user, false, visibilityChanged)) | ||
user = unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2}) | ||
assert.True(t, user.KeepActivityPrivate) | ||
|
||
newEmail := "new_" + user.Email | ||
user.Email = newEmail | ||
assert.NoError(t, user_model.UpdateUser(db.DefaultContext, user, true)) | ||
assert.NoError(t, user_model.UpdateUser(db.DefaultContext, user, true, false)) | ||
user = unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 2}) | ||
assert.Equal(t, newEmail, user.Email) | ||
|
||
user.Email = "no [email protected]" | ||
assert.Error(t, user_model.UpdateUser(db.DefaultContext, user, true)) | ||
assert.Error(t, user_model.UpdateUser(db.DefaultContext, user, true, false)) | ||
} | ||
|
||
func TestUpdateUserEmailAlreadyUsed(t *testing.T) { | ||
|
@@ -373,7 +374,7 @@ func TestUpdateUserEmailAlreadyUsed(t *testing.T) { | |
user3 := unittest.AssertExistsAndLoadBean(t, &user_model.User{ID: 3}) | ||
|
||
user2.Email = user3.Email | ||
err := user_model.UpdateUser(db.DefaultContext, user2, true) | ||
err := user_model.UpdateUser(db.DefaultContext, user2, true, false) | ||
assert.True(t, user_model.IsErrEmailAlreadyUsed(err)) | ||
} | ||
|
||
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
It confuses me, why
visibilityChanged
meanscheckVisibility
? Even if it is correct, it's hard to understand.As a quick patch, this PR might work.
But I think it reduces maintainability, I can't imagine what does
UpdateUser(ctx, u, false, false)
orUpdateUser(ctx, u, false, true)
do without reading all related code.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.
How about add an error handling after calling
validateUser
instead of addcheckVisibility
tovalidateUser
?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.
That means the previous value which have stored in database should not be checked, only changed values need to be checked .
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.
I can understand after I spend much time on reading code, while I do not think it is a good design.
Now we have
(..., true, false)
, do we want to have(..., true, false, true)
in the future?