LDAP: determine shares of offline users only when needed#27698
Merged
Conversation
- determine shares may via Sharing code result in user exists checks - this may result in an infinite loop when user exists was called before - the info is really only required at one occ command Signed-off-by: Arthur Schiwon <blizzz@arthur-schiwon.de>
Member
Author
|
/backport to stable22 |
Member
Author
|
/backport to stable21 |
Pytal
approved these changes
Jun 28, 2021
Member
|
Drone 🤷♂️ |
Member
Author
unrelated |
This was referenced Jun 28, 2021
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The story behind is this:
OfflineUser)OfflinerUsertriggered fetching all detailsBut the only place where we need the information is the
ldap:show-remnantscommand.fixes a segfault on a migration step of accessibility app on upgrade
#25761(wrong issue)