Skip to content
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

Make sure we do not renotify notifications when we have received the same etag as during the last check #6970

Merged
merged 2 commits into from
Sep 12, 2024

Conversation

claucambra
Copy link
Collaborator

Do this regardless of what the server's response is

@claucambra claucambra self-assigned this Aug 6, 2024
Copy link

sonarcloud bot commented Aug 6, 2024

@mgallien
Copy link
Collaborator

/backport to stable-3.14

…same etag as during the last check

Do this regardless of what the server's response is

Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
This prevents situations where the server does not provide an etag header. This would make the empty pre-fetch and empty post-fetch etag headers match, meaning notifications would never be notified

Signed-off-by: Claudio Cambra <claudio.cambra@nextcloud.com>
@mgallien mgallien force-pushed the bugfix/prevent-renotification branch from 9941315 to 6b0e485 Compare September 12, 2024 07:52
@mgallien mgallien enabled auto-merge September 12, 2024 07:53
@nextcloud-desktop-bot
Copy link

AppImage file: nextcloud-PR-6970-6b0e485ab9b3b9f2a25bda325144cfaa7e0ff67a-x86_64.AppImage

To test this change/fix you can simply download above AppImage file and test it.

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

Copy link

sonarcloud bot commented Sep 12, 2024

@mgallien mgallien merged commit 4cd63d8 into master Sep 12, 2024
13 of 15 checks passed
@mgallien mgallien deleted the bugfix/prevent-renotification branch September 12, 2024 08:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants