OpenListTeam / OpenListTeam/OpenList

[BUG] mege网盘列出了已经删除的文件

Open
#1,914 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
Go
Stars
24.7k
Forks
2.3k
Avg merge
1d 20h
Merged PRs (30d)
36

Description

Please confirm the following
  • I have read and agree to AGPL-3.0 Section 15 .
    The program is provided "as is" without any warranties; you bear all risks of using it.

  • I have read and agree to AGPL-3.0 Section 16 .
    The copyright holders and distributors are not liable for any damages resulting from the use or inability to use the program.

  • I confirm my description is clear, polite, helps developers quickly locate the issue, and complies with community rules.

  • I have read the OpenList documentation.

  • I confirm there are no duplicate issues or discussions.

  • I confirm this is an OpenList issue, not caused by other reasons (such as network, dependencies, or operation).

  • I believe this issue must be handled by OpenList and not by a third party.

  • I confirm this issue is not fixed in the latest version.

OpenList Version (required)

v4.1.9

Storage Driver Used (required)

mega

Bug Description (required)
1. 挂载mega网盘 关闭 [move to trash](https://github.com/OpenListTeam/OpenList/actions/runs/20689978534)

2.上传一个50M的文件

3.查看一下占用的空间 空间显示正常

4. 删除这个文件 (永久删除)

5.查看一下占用的空间 空间显示正常

6. 回到mega网盘 点击刷新按钮 那个已经被删除的文件又会被显示出来

8. 选择这个已经删除的文件 再次删除 提示 Object (typically, node or user) not found

9.存储中点击禁用mega网盘 再次开启  这时候那个被删除的文件才会消失不见

Logs (required)

可能和缓存有关系

./openlist version
Built At: 1/4/2026, 8:12:30 AM
Go Version: go1.25.1 darwin/arm64
Author: The OpenList Projects Contributors noreply@openlist.team
Commit ID: 345c7f92d2527ee1212c1d3d58f5a7c9ba656cca
Version: refs/pull/1913/merge
WebVersion: rolling

Configuration File Content (required)

..

Reproduction Link (optional)

No response

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue with the mega storage driver using the listed upload, permanent-delete, refresh, and disable/re-enable steps. Inspect the refresh and caching path implicated by the report. Done means a permanently deleted file disappears after refresh without disabling and re-enabling the storage, and a second delete does not report that the object is missing.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
38/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.