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 小時 25 分鐘
- 30 天內合併 PR
- 213
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
fglock/PerlOnJava 的其他 Issue
-
難度 2/5 1-3 小時 新手友好度 68/100
fglock/PerlOnJava#1651 ·
維護者通常 1 天內回覆
-
bug
難度 2/5 1-3 小時 新手友好度 72/100
fglock/PerlOnJava#1579 ·
維護者通常 1 天內回覆
-
area:cpan-port area:unicode bug
難度 2/5 1-3 小時 新手友好度 88/100
fglock/PerlOnJava#1341 ·
維護者通常 1 天內回覆
-
難度 3/5 半天 新手友好度 45/100
fglock/PerlOnJava#1808 ·
維護者通常 1 天內回覆
-
area:cpan-port area:runtime bug
難度 4/5 3-5 天 新手友好度 28/100
fglock/PerlOnJava#1802 · 1 則留言 ·
維護者通常 1 天內回覆
查看 fglock/PerlOnJava 的全部 Issue
相似的 Issue
-
Add .gitattributes so share/skel keeps LF on a Windows git checkout可能已有人在做 @sadhana-s-codez 於 1 天前認領。 未關閉
難度 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
-
難度 2/5 1-3 小時 新手友好度 69/100
bioconda/bioconda-recipes#70187 ·
維護者通常 2 天內回覆