Concurrent renaming of the same file on the server and client results in duplicate files without conflict detection
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
調査の方向性
The payload names no source files or tests, so start by reproducing the rename-on-both-sides scenario from the steps in the issue with a local server and a desktop client, then find where the client's sync engine compares local and remote rename operations. Done means the concurrent rename is either detected and reported as a conflict or the maintainers agree on the intended merge behaviour, and the activity log shows both operations. Expect design discussion before a patch.
索引モデルが issue の本文から書いたものです。
説明
[DC-410]
Pre-submission Checks
- I checked for similar issues, but could not find any. I also checked the closed issues. I could not contribute additional information to any existing issue.
- I will take the time to fill in all the required fields. I know that the bug report may be dismissed otherwise due to lack of information.
Describe the bug
When the same file is renamed independently on the server and the desktop client before the server-side rename has synchronised to the client, both renamed versions appear as separate files after synchronisation completes.
For example:
- A file named
test19exists in a synchronised folder on both the server and the local client. - Rename
test19totest30directly on the server. - Before this change is synchronised to the desktop client, rename the still-existing local file
test19totest31. - Allow synchronisation to complete.
After synchronisation, both test30 and test31 appear as separate files on the server and in the local synchronised folder.
However, these are two different names resulting from renaming the same original file. No conflict is detected or reported, despite both rename operations targeting the same original file.
This behavior also seem to appear because of the delay on server to client synchronization
Expected behavior
Changes made directly on the server should be automatically detected and synchronised to the connected desktop client without requiring manual intervention.
When the same original file is renamed independently on the server and the desktop client before the initial change has synchronised, the client should detect and appropriately handle the conflicting changes.
It should not silently result in two separate files containing identical content without reporting or handling the conflict.
The activity history should also accurately represent the operations performed.
Steps to reproduce the issue
- Connect the ownCloud desktop client and the server using the same account.
- Ensure that a file named
test19exists in a synchronised folder on both the server and the local client. - Rename
test19totest30directly on the server through the web interface. - Before the server-side rename is synchronised to the desktop client, rename the still-existing local file
test19totest31using the local file manager. - Allow the desktop client to complete synchronisation or manually click on "Sync Now" from the desktop client
- Check the corresponding folder on the server and the local client.
- Observe that both
test30andtest31exist as separate files. - Check the desktop client's activity history.
- Observe that only one rename operation is displayed and no conflict is reported.
Screenshots
- Both test30 and test31 appear as separate files on the server and in the local synchronised folder.
- No conflict is detected or reported.
- No conflict copy is created.
https://github.com/user-attachments/assets/0f6dfda4-5249-4c9c-a979-b2652ca2f71e
The activity history on reproducing showed the following details
Logs
No response
Client version number
ownCloud desktop client: 7.2.0.19922-rc.3
Desktop environment (Linux only)
Ubuntu 24.04.5 LTS.
Client package version and origin (Linux only)
Installed Linux app image from https://download.owncloud.com/desktop/ownCloud/testing/7.2.0.19922-rc.3/linux-appimage/
Installation path (Windows only)
No response
Server information
Server: ownCloud Infinite Scale (oCIS)
Server version: 8.2.0+42f7fdcfee2
Web UI: ownCloud Web UI 12.5.0
Server execution: Built from binary and running using ocis/bin/ocis server.
Additional context
Additional observation
Synchronisation behaviour appears to differ depending on the direction of the change:
Test scenario:
- Ensure that a file named
Test22exists on both the server and the local client. - Rename Test22 to
Test10on the local client. - Rename Test22 to
Test15directly on the server before the client-side change has fully synchronised. - Allow synchronisation to complete.
- Check the resulting filename on both the server and the local client.
Observed behavior:
- After synchronisation, both the server and the local client contain the file named Test15.
In this scenario, both locations eventually reflect the same filename, and no duplicate files are observed.
https://github.com/user-attachments/assets/1fa4b65d-2400-4042-806c-733deb208754
- 主要言語
- C++
- スター
- 1.5k
- フォーク
- 695
- 平均マージ
- 8日 7時間
- マージ済み PR(30日)
- 6
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
owncloud/client のほかの issue
-
難易度 4/5 3〜5日 初心者へのやさしさ 35/100
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
メンテナーはふだん 1 日以内に返信
-
Account removal silently keeps the local sync folder, so re-adding creates ownCloud (2), (3), …対応中かも @Eiji-Kondo が 8 日前に担当しました。 オープン
難易度 5/5 1週間以上 初心者へのやさしさ 25/100
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 48/100
メンテナーはふだん 1 日以内に返信
-
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
メンテナーはふだん 1 日以内に返信
owncloud/client の issue をすべて見る
似ている issue
-
needs-format
難易度 2/5 1〜3時間 初心者へのやさしさ 82/100
Niko1221/Strata#6251 · コメント 1 件 ·
メンテナーはふだん 5 日以内に返信
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
metasequoiaime/msime#11666 ·
メンテナーはふだん 1 日以内に返信
-
DAE2 crashes on call.without.effects with a non ref.func expression対応中かも @stevenfontanella が今日担当しました。 オープン
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
WebAssembly/binaryen#9404 ·
メンテナーはふだん 1 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
CodeZombie/goodluckOS#178 ·
-
難易度 2/5 1〜3時間 初心者へのやさしさ 66/100
CVO-Org/immersive-cigs-rewrite#313 ·
メンテナーはふだん 1 日以内に返信