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

未关闭
#12,682 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
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 内容生成。

描述

[DC-425]

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 小时
30 天内合并 PR
6

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

owncloud/client 的其他 Issue

查看 owncloud/client 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。