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

Regression: most changes don't get pushed to other clients after update to NC 29.0.5 #514

Open
LostinSpacetime opened this issue Aug 25, 2024 · 7 comments

Comments

@LostinSpacetime
Copy link

LostinSpacetime commented Aug 25, 2024

My installation:
NC 29.0.5
CP 0.7.0
Deck 1.13.1

self-test output:

✓ redis is configured
✓ push server is receiving redis messages
✓ push server can load mount info from database
✓ push server can connect to the Nextcloud server
✓ push server is a trusted proxy
✓ push server is running the same version as the app

After a recent update (maybe NC 29.0.5) new comments on a Deck card are not being updated on other clients. To trigger the update, one (editor or any other client) have to reload the page or simply change the browser-tab and back. This behavior is consistent with different browsers (Firefox and Chromium) and OSs (Fedora 40 and Windows 11) 100% reproducible.

@LostinSpacetime LostinSpacetime changed the title Regression: new comments don't get pushed to other clients Regression: most changes don't get pushed to other clients Aug 25, 2024
@LostinSpacetime
Copy link
Author

After more testing, it seems most events are ignored and not pushed to clients. I tested with files and folders renaming, creating and deleting. The changes done by the editor are not shown on other clients until a site reload.

@LostinSpacetime LostinSpacetime changed the title Regression: most changes don't get pushed to other clients Regression: most changes don't get pushed to other clients after update to NC 29.0.5 Aug 25, 2024
@LostinSpacetime
Copy link
Author

LostinSpacetime commented Sep 4, 2024

The problem persists with NC 29.0.6 and NC 29.0.7

@icewind1991
Copy link
Member

Can you check the output of occ notify_push:metrics to see if the push server is receiving events and/or sending updates.

@LostinSpacetime
Copy link
Author

LostinSpacetime commented Sep 17, 2024

I updated to NC 30.0.0 and have the same issue.
Output of occ notify_push:metrics is

Active connection count: 5
Active user count: 5
Total connection count: 8546
Total database query count: 436
Events received: 74466
Messages sent: 9834

In Deck, I see the connected accounts on the top and added, moved, renamed cards are pushed to all clients. When I comment a card on one client though, nothing happens, even if the number of Events received and Messages sent raise by 5. It's enough to change the tab to trigger the refresh on all clients. I tested this with multiple browsers on multiple devices with the same behavior.

When I change the content of a shared folder in Files, the changes are not shown in other clients. Again, the number of Message received and sent changes, but with no visible effect until a page reload. Changing tabs doesn't trigger the refresh in this case.

This used to work, and I'm pretty sure it was the update to NC 29.0.5 that broke it.

@LostinSpacetime
Copy link
Author

Can anyone reproduce this problem, or is it my setup?

@MrRinkana
Copy link
Contributor

Can you run the test-client? Did you change anything on the reverse proxy? The service is running, no errors in the systemd journal?

@LostinSpacetime
Copy link
Author

Can you run the test-client? Did you change anything on the reverse proxy? The service is running, no errors in the systemd journal?

As I've posted above, the self-test as well as the metrics look perfect. There aren't any errors from the service. When I installed notify-push, I only ran the quick setup script and everything worked as expected for several months until the update to 29.0.5. When I noticed that, I ran the self-test and got the warning, that my service is out of date since the App got the update to 0.7.0. After restarting the service, the self-test ran without issues, but the problem persisted.

I didn't use the test-client, but I will as soon I have some time, probably this weekend.

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

No branches or pull requests

3 participants