Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[Bug]: F-34 Files: a cancelled directory fetch is logged as an error and can leave an error state behind

未关闭 适合新手
#65,090 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
78/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript
领域
frontend

调研方向

从 apps/files/src/views/FilesList.vue 中的 fetchContent() 开始,追踪每个请求的 AbortController 如何影响 catch 和 finally。确认已取消的请求会在 debug 级别处理,而不会覆盖当前的错误或加载状态。完成标准是:在 All files 和 Deleted files 之间快速切换时不再记录错误,也不会让较新的 fetch 处于错误状态。

由索引模型根据 Issue 内容生成。

描述

0. Needs triage 35-feedback bug
⚠️ This issue respects the following points: ⚠️
  • This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
  • This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
  • I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
  • I agree to follow Nextcloud's Code of Conduct.
  • I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.
Bug description

F-34 · Files: a cancelled directory fetch is logged as an error and can leave an error state behind

Repository nextcloud/server
Severity Low (console error; in a race, the error message or a finished loading state of the old request)
Component apps/files/src/views/FilesList.vue (fetchContent())
Affects 35.0.1
Verified Chrome DevTools on a production instance (switching between All files and Deleted files right after a delete)

What happens

After deleting files and switching views quickly, the console shows

[DEBUG] files: Cancelled previous ongoing fetch
[ERROR] files: Error while fetching content  {error: …}

Cause

fetchContent() aborts the running request when a new one starts. The aborted request rejects,
and its catch treats the abort like any other failure:

  • it logs Error while fetching content at error level,
  • it sets this.error, after the new request already reset it,
  • its finally sets loading = false while the new request is still running.

Fix

Each call keeps its own AbortController. When the request was aborted, the catch only logs at
debug level and leaves the state alone; finally touches loading only when the call is still the
current one.

Steps to reproduce

see the top

Expected behavior

see the top

Nextcloud Server version

35

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

Is this bug present after an update or on a fresh install?

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?
  • Default user-backend (database)
  • LDAP/ Active Directory
  • SSO - SAML
  • Other
Configuration report

List of activated Apps

Nextcloud Signing status

Nextcloud Logs

Additional info

No response

主要语言
PHP
星标
37k
派生
5.3k
平均合并
2 天 6 小时
30 天内合并 PR
702

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

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

nextcloud/server 的其他 Issue

查看 nextcloud/server 的全部 Issue

相似的 Issue

更多 PHP Issue

把新 issue 发到你的邮箱

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