fix: make sure background threads check for not logged in current user #16402
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.
Summary
After the user refactoring in #15727, some places where a separate/background thread is accessing the current user, it will fail because they now have to check for absence of/no user, before calling
CurrentUserUtil.getCurrentUserDetails/getCurrentUsername
.This PR fixes one such issue in the
DefaultMessageService
.Automatic test
MessageServiceTest#testSendMessageWithNoCurrentUser()