nextcloud / nextcloud/updater

In low memory setups, the updater fails at step 5

Open
#505 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: integrity mode: web
Dominant language
PHP
Stars
51
Forks
40
Avg merge
2d 19h
Merged PRs (30d)
3

Description

In low memory setups, the upgrader fails at step 5. The other steps work without problems.

Solution: The updater should either provide

  1. a low memory version to verify the integrity of the downloaded zip file at step 5 or
  2. provide a way for users to continue at step 5 without successful verification of the zip file (there should be a not about where to find the downloaded zip file an how to verify the integrity of the ZIP file yourself before letting the updater continue)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the failure at updater step 5 in a low-memory setup and trace the ZIP integrity verification involved there. Done means users can complete the update reliably under low memory, or can continue after verification with clear instructions for locating and checking the downloaded ZIP.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
release
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.