Overlay icons show "sync" instead of the warning (yellow) or error (red) icon for sync errors.

オープン
#12,682 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
3/5
見積もり時間
1〜2日
初心者へのやさしさ
55/100
issue の種類
バグ
明瞭さ
おおむね明確
活発さ
活発
技術スタック
cpp
領域
desktop

調査の方向性

Start by tracing how the desktop client maps ignored, excluded, and blacklisted file statuses to Windows overlay icons. Reproduce the invalid-name warning and quota-error cases described in the issue, then locate the relevant overlay status handling and tests. Done when those cases show the expected yellow warning or red error icon instead of sync arrows.

索引モデルが issue の本文から書いたものです。

説明

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

Files that the client reports as ignored, excluded or failed show the sync overlay icon in the local sync folder instead of the yellow warning triangle or the red error icon.

Yellow warning triangle: files with names that are not valid on Windows are listed in the client's errors list as ignored or excluded, but their overlay icon is sync instead of yellow warning triangle.

Red error icon: a 600 MB file is added to an account with a 1 GB quota that is already almost used up. The upload fails with error in client as blacklisted but the overlay icon is sync arrows instead of red error icon.

Expected behavior

Files that are not synced because of a problem, such as an invalid name, should show the yellow warning triangle.

Files and folders that are not synced because of a fatal problem should show the red error icon.

Steps to reproduce the issue

Yellow warning triangle

  1. Connect the ownCloud desktop client to the server and let the local sync folder sync fully.
  2. Open the local sync folder and add a problematic file, for example a file with a trailing dot, a file with a trailing space, or a file with a reserved name.
  3. The client lists the files as ignored or excluded in error section, but they show the sync icon instead of the yellow warning triangle in local sync folder.

Red error icon

  1. Connect the desktop client to its server.(preferably login to account with small quota set)
  2. Open the local sync folder and create a fatal problem, for example by adding files that are larger than the available quota.
  3. The client shows the quota error for the file with status blacklisted, but it shows the sync icon instead of the red error icon.
Screenshots

The red boxes in local sync shows overlay icons, and the notes beside tells what should have been there.

  1. The files with invalid names show the sync icon instead of the yellow warning triangle. The client shows them with the "i" icon in the Errors section with status file ignored or excluded.
  2. fill2.bin shows the sync icon instead of the red error icon. The client shows it with the "x" icon in the Errors section with status blacklisted.
Image
Logs

No response

Client version number

ownCloud 7.2.0.19922-rc.3 584b08
Libraries Qt 6.8.3, OpenSSL 3.4.5 7 Apr 2026
Using virtual files plugin: wincfapi
OS: windows-10.0.26200 (build arch: x86_64, CPU arch: x86_64)
QPA: windows

Desktop environment (Linux only)

No response

Client package version and origin (Linux only)

No response

Installation path (Windows only)

C:\Program Files\ownCloud

Server information

Server: ownCloud Infinite Scale (oCIS)
Server version: 8.2.0
Web UI: ownCloud Web UI 12.5.0
Server execution: Running in Docker (docker compose) on Ubuntu 24.04.5 LTS, using the image owncloud/ocis:8.2.0

Additional context

The test case describes uploading files and folders with path longer than 255 characters causes error when syncing. But that does not cause an error, even when long paths are disabled in Windows. The file syncs and shows the green tick.

主要言語
C++
スター
1.5k
フォーク
695
平均マージ
8日 7時間
マージ済み PR(30日)
6

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

owncloud/client のほかの issue

owncloud/client の issue をすべて見る

似ている issue

C++ の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。