-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
Lower some session warnings to debug level #41195
Conversation
Signed-off-by: Git'Fellow <12234510+solracsf@users.noreply.github.com>
/backport to stable27 |
/backport to stable26 |
Are either of the changes in this PR for the specific message being spammed in #41156? The message in that issue seems to be:
|
@@ -802,12 +802,11 @@ private function validateToken($token, $user = null) { | |||
'app' => 'core', | |||
'user' => $dbToken->getUID(), | |||
]); | |||
|
|||
return false; | |||
} | |||
|
|||
if (!$this->checkTokenCredentials($dbToken, $token)) { |
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.
inside this method there are critical paths that might still be worth logging. That is every time \OC\Authentication\Token\IProvider::invalidateToken
or markPasswordInvalid
is called, for example.
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.
Maybe in a follow up PR? Otherwise, feel free to commit them as output messages would require a deeper knowledge of what they exactly accomplish, which I don't have. 🦺
Closing as #41302 has been merged. |
Summary
No need to Warn about these, and they can be noisy.
Resolves #41156
Checklist