nextcloud / nextcloud/notify_push
Warn if notify_push daemon is not running ?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
For some reasons, the notify_push daemon wasn't running anymore on our instance. That didn't throw any error, and seems not to be logged anywhere.
Consequences : talk notifications were not working at all, or very very very slowly (several minutes).
systemctl enable --now notify_push solves the problem instantly. But it takes me hours to figure it out.
Maybe the client push app should warn somewhere if the daemon is not running ?
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 tracing how notify_push starts and how its health or availability is exposed to the Nextcloud client; the payload names no files or tests. Determine where a stopped daemon can be detected and define a user-visible warning for unavailable or delayed talk notifications, with coverage for the failure case.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, observability
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100