OpenListTeam / OpenListTeam/OpenList
[BUG] 通过离线下载方式添加文件,无法触发全局目录更新钩子,strm驱动没有自动更新
Nobody has claimed this yet.
- 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.2.1 (Commit: 8d39d63) - Frontend: v4.2.1 - Build at: 2026-04-09 14:27:23 +0000
使用的存储驱动(必填)
中国移动云盘、onedriveapp都进行了尝试
问题描述(必填)
通过离线下载方式添加文件,无法触发全局目录更新钩子,下载完成后,文件上传成功了,但是没有触发钩子,导致strm存储没有自动更新
我理解从云盘app直接添加文件绕过了openlist导致strm不会更新
但离线下载也是openlist的功能,其先下载后上传,走的应该也是openlist的上传才对,那应该可以触发更新钩子,但现在与我的预期不符
经过测试,直接上传是可以触发更新钩子的,只有离线下载不行
日志(必填)
没找到,看容器日志只有这个
INFO[2026-04-18 11:46:23] reading config file: /opt/openlist/data/config.json INFO[2026-04-18 11:46:23] load config from env with prefix:
INFO[2026-04-18 11:46:23] max buffer limit: 799MB
INFO[2026-04-18 11:46:23] mmap threshold: 4MB
INFO[2026-04-18 11:46:23] init logrus...
start HTTP server @ 0.0.0.0:5244
配置文件内容(必填)
全局目录更新钩子已开启
以下为strm驱动配置
{"id":14,"mount_path":"/共享存储/影视飓风【Strm】/影视飓风","order":1,"driver":"Strm","cache_expiration":0,"custom_cache_policies":"","status":"work","addition":"{\"paths\":\"/共享存储/影视飓风【只读】/影视飓风\",\"siteUrl\":\"\",\"PathPrefix\":\"\",\"downloadFileTypes\":\"ass,srt,vtt,sub,strm\",\"filterFileTypes\":\"mp4,mkv,flv,avi,wmv,ts,rmvb,webm,mp3,flac,aac,wav,ogg,m4a,wma,alac\",\"encodePath\":false,\"withoutUrl\":true,\"withSign\":false,\"SaveStrmToLocal\":true,\"SaveStrmLocalPath\":\"/opt/openlist/strmfiles\",\"SaveLocalMode\":\"update\",\"Version\":5}","remark":"","modified":"2026-04-10T17:45:50.175548308+08:00","disabled":false,"disable_index":false,"enable_sign":false,"order_by":"","order_direction":"","extract_folder":"","web_proxy":false,"webdav_policy":"native_proxy","proxy_range":false,"down_proxy_url":"","disable_proxy_sign":false}
复现链接(可选)
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue with offline download enabled, the global directory update hook, and the configured Strm driver. Trace the offline download completion path and compare it with the direct upload path to determine whether the hook is invoked after the file is uploaded. Done means offline downloads trigger the same directory update and Strm refresh as direct uploads.
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
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100