Don't say "No update available." when updater_server fails
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
Currently the updater_server service always(?) fails with HTTP code 500, see: https://github.com/nextcloud/updater_server/issues/698
However, the updater seems to interpret this as "no update available" and suggests a manual update, which is misleading. (I've seen some forum entries where this has caused problems, it cost me quite some time, and it might even lead to people damaging their instances trying to upgrade manually).
I'm not sure if this affects Nextcloud (server) as well, it somehow found out there's an update and showed the correct version. (Does is have a different way to search for updates?)
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 the updater's handling of the updater_server HTTP 500 response described in issue #698. Confirm how that failure becomes "no update available" and define done as presenting an error or otherwise distinguishing the failed service from a genuine lack of updates, with the relevant behavior covered by a test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend, release
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100