OpenListTeam / OpenListTeam/OpenList

[BUG] 添加新的复制任务,会导致旧复制任务重新获取链接

Open
#2,172 0 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

请确认以下事项
  • 我已确认阅读并同意 AGPL-3.0 第15条
    本程序不提供任何明示或暗示的担保,使用风险由您自行承担。

  • 我已确认阅读并同意 AGPL-3.0 第16条
    无论何种情况,版权持有人或其他分发者均不对使用本程序所造成的任何损失承担责任。

  • 我确认我的描述清晰,语法礼貌,能帮助开发者快速定位问题,并符合社区规则。

  • 我已确认阅读了OpenList文档

  • 我已确认没有重复的问题或讨论。

  • 我已确认是OpenList的问题,而不是其他原因(例如 网络依赖操作)。

  • 我认为此问题必须由OpenList处理,而非第三方。

  • 我已确认这个问题在最新版本中没有被修复。

  • 我没有阅读这个清单,只是闭眼选中了所有的复选框,请关闭这个 Issue 。

OpenList 版本(必填)

v4.1.1

使用的存储驱动(必填)

quark/smb

问题描述(必填)

我不确定新版本是否已解决,因为我搜不到相关issue,由于问题是概率出现,我也暂时没在新版本复现出来

添加了两个存储,夸克和smb,复现步骤

  1. 从夸克复制文件A到smb,生成一个任务
  2. 在夸克中删除文件A
  3. 从夸克复制文件B到smb,生成一个新任务
  4. 此时任务A有可能触发重新获取文件,又因文件已被删除,导致复制失败报错
    link: failed get link: invalid file [68ab6a5bac514021972a4af65eb4b50b]
日志(必填)
Image
配置文件内容(必填)
version: '3.3'
services:
  openlist:
    image: openlistteam/openlist:v4.1.1
    volumes:
      - /vol1/1000/apps/openlist/data:/opt/openlist/data
    ports:
      - 5244:5244

添加quark和smb存储

复现链接(可选)

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 reported sequence with Quark and SMB on OpenList v4.1.1: copy file A, delete it, then copy file B and observe whether task A refreshes its link. No source files or tests are named, so trace the copy-task and link-fetching flow from that reproduction. Done means creating a new copy task no longer causes the earlier task to fetch a deleted source unexpectedly, with regression coverage for the sequence.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.