Catalyst upload tempfile is deleted during request in #1642 integration
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
调研方向
Start with t/aggregate/live_engine_request_uploads.t, the test that fails with 'Upload temp file was deleted' in the integration run. The issue says the work depends on #1642 landing first, so wait for its final commit before reproducing. Done means that test passes on that commit and the lost ownership edge for the File::Temp object is covered by a focused regression test.
由索引模型根据 Issue 内容生成。
描述
Summary
The #1642 cleanup changes appear to introduce a Catalyst upload lifetime regression. Please triage after #1642 is merged or its implementation settles; this report records integration evidence and avoids duplicating the cleanup implementation.
Reproduction and evidence
In a disposable integration checkout merging PerlOnJava3 PR #1777 (47e9bfb78f1ac790143838fafcf92f852147bc2b) with the #1642 work in PerlOnJava5 PR #1746 (46d9200e5553bc645fe38b4ee341433aff8ae958), the Catalyst release acceptance target reached 3,819/3,820 passing tests and failed:
t/aggregate/live_engine_request_uploads.t:Upload temp file was deleted.- During global destruction, the runtime also reported
DESTROY created new reference to dead object 'File::Temp'.
This failure occurred only in the integration run; the PerlOnJava3 #1777 branch's earlier Catalyst acceptance run passed 3,733 tests. The integration build was b124844c9 (test-only merge commit); neither review branch was changed. Because this is a tempfile lifetime/destructor failure, it may have a different root cause from the Mojolicious request and WebSocket failures; it is tracked separately for that reason.
Expected behavior
A Catalyst upload's temporary file remains available for the documented request lifetime and is cleaned up only after its final owner is gone. Global destruction must not resurrect or dereference an already-dead File::Temp object.
Requested follow-up
After #1642 lands, rerun the named test against its final commit, identify which ownership edge is lost, and add focused permanent regression coverage before changing lifecycle cleanup behavior. The run had no output for 600 seconds while waiting on DBIx::Class's _dbictest_global.lock, so it was stopped by the target soft timeout; no conclusion about DBIx::Class regressions is claimed here.
- 主要语言
- Perl
- 星标
- 64
- 派生
- 7
- 平均合并
- 5 小时 31 分钟
- 30 天内合并 PR
- 214
环境准备
- 提供 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
fglock/PerlOnJava 的其他 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 72/100
fglock/PerlOnJava#1579 ·
维护者通常 1 天内回复
-
难度 3/5 1-2 天 新手友好度 48/100
fglock/PerlOnJava#1835 ·
维护者通常 1 天内回复
-
area:cpan-port bug
难度 3/5 1-2 天 新手友好度 68/100
fglock/PerlOnJava#1820 ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 45/100
fglock/PerlOnJava#1808 ·
维护者通常 1 天内回复
-
area:cpan-port area:runtime bug
难度 4/5 3-5 天 新手友好度 28/100
fglock/PerlOnJava#1802 · 2 条评论 ·
维护者通常 1 天内回复
查看 fglock/PerlOnJava 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 80/100
jimsalterjrs/sanoid#1116 · 1 个 reaction ·
-
Add .gitattributes so share/skel keeps LF on a Windows git checkout可能已有人在做 @sadhana-s-codez 于 2 天前认领。 未关闭
难度 1/5 1 小时以内 新手友好度 85/100
PerlDancer/Dancer2#1854 · 1 条评论 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 78/100
major/MySQLTuner-perl#1007 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
-
难度 1/5 1 小时以内 新手友好度 88/100