Skip to content

fix(logs): no new notification should not be a warning in logs - #10653

Merged
mgallien merged 1 commit into
masterfrom
bugfix/removeSpamInLogs
Aug 24, 2026
Merged

fix(logs): no new notification should not be a warning in logs#10653
mgallien merged 1 commit into
masterfrom
bugfix/removeSpamInLogs

Conversation

@mgallien

Copy link
Copy Markdown
Collaborator

adjust log level while making sure we do not loose information when querying notifications and they did not change

Resolves

#

Summary

TODO

  • ...

Checklist

AI (if applicable)

@mgallien

Copy link
Copy Markdown
Collaborator Author

/backport to stable-34.0 please

adjust log level while making sure we do not loose information when
querying notifications and they did not change

Signed-off-by: Matthieu Gallien <matthieu.gallien@nextcloud.com>
@mgallien
mgallien enabled auto-merge August 24, 2026 16:06
@mgallien
mgallien force-pushed the bugfix/removeSpamInLogs branch from 36b6114 to 9e226e2 Compare August 24, 2026 16:06
@github-actions

Copy link
Copy Markdown
Contributor

Artifact containing the AppImage: nextcloud-appimage-pr-10653.zip

Digest: sha256:599edc558bc838cefeb6304f2b15b06c90096f7ea4975daae30d483c1a1958c0

To test this change/fix you can download the above artifact file, unzip it, and run it.

Please make sure to quit your existing Nextcloud app and backup your data.

@sonarqubecloud

Copy link
Copy Markdown

@mgallien
mgallien merged commit 9f1a02d into master Aug 24, 2026
24 checks passed
@mgallien
mgallien deleted the bugfix/removeSpamInLogs branch August 24, 2026 16:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants