Move new files in place: Could not rename ...
Open
Nobody has claimed this yet.
bug
feature: moving
hotspot: rename / rmdir
- Dominant language
- PHP
- Stars
- 51
- Forks
- 40
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 3
Description
The last 2 times I've used the updater I've been getting stuck here:
I have to manually click the "Retry" button like 16 million times and it completes, apparently fine, and checking the version when it's done shows it's the latest version. Any solution to this? I'm getting carpal tunnel in my right index finger. :p
I'm using the containerized version:
nextcloud:
# https://hub.docker.com/r/linuxserver/nextcloud
image: linuxserver/nextcloud:latest
container_name: nextcloud
hostname: nextcloud
environment:
- TZ='America/Chicago'
volumes:
- "scotts_nextcloud:/config" # Nextcloud Configs
- "/i/Nextcloud:/data" # Storage area
restart: unless-stopped
networks:
- ocs
- odb
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 updater's “Move new files in place” step with the containerized Nextcloud setup shown in the issue. Investigate why the rename operation repeatedly requires pressing Retry; done means the update completes without repeated manual retries.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, php
- Domain
- devops, release
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100