nextcloud / nextcloud/notify_push
Regression: most changes don't get pushed to other clients after update to NC 29.0.5
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with NC 29.0.5, CP 0.7.0, and Deck 1.13.1 using the listed self-test checks, then trace the push-notification path for new Deck comments. Compare behavior across the reported browsers and operating systems; done means comments update other clients without a page or tab reload.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100