nextcloud / nextcloud/notify_push
Unsharing a file does not trigger a delete event on the sharee device
Open
Nobody has claimed this yet.
bug
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
user1shares a file withuser2- without a polling event the file is synced in
user2desktop user1unshares the file- the file is not deleted from
user2desktop. Only a polling event deletes the file.
Environment:
Desktop Client: 3.7.1
Server: 25.0.3
notify_push: 0.5.2
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
Start by reproducing the four-step sharing and unsharing sequence with the listed Desktop Client, Server, and notify_push versions. Trace how the unshare notification reaches user2 without relying on a polling event. Done means the file is deleted from user2's desktop immediately after user1 unshares it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100