fix(loader-server): a watch restart forks the new worker before the old one exits
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 72/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- bun, node.js, typescript
- 領域
- backend
研究方向
Start with apps/server/src/server.ts at the cited restart path, then trace how the child worker is forked and how restart is triggered. Check the project’s existing process and logging tests, if present. Done means restart waits for the old worker to exit before forking, kills it after a timeout if needed, and logs child exit and error events.
由索引模型根據 Issue 內容生成。
描述
Which app is this bug report for?
server
Issue description
On restart, child.kill() only sends SIGTERM and fork runs right after (server.ts#L43-L50).
- If the old game server still holds its port (4444/4445 in
nf new --serverprojects), the new worker fails withEADDRINUSE. - If a game ignores SIGTERM, the old worker is never killed.
- No
exit/errorhandler is attached to the child, so worker crashes go unreported (the editor isn't told either).
Found by reading the code path (not reproduced).
Expected: the new worker starts only once the old one has exited, and worker exits and errors are logged.
Suggested fix: wait for the old child's exit event (SIGKILL after a timeout) before forking, and log exit and error.
Found during a read-only audit of main @ 044c766 (2026-11-11).
Code sample
if (child) {
child.kill(); // SIGTERM, not awaited
child = undefined;
}
child = fork(join(dirname(__filename), "worker.js"), ...);
Versions
- @nanoforge-dev/loader-client / @nanoforge-dev/loader-server / @nanoforge-dev/loader-website 1.7.0 (
main@ 044c766) - Bun 1.3.14
- Linux x86_64
Issue priority
Medium (should be fixed soon)
I have tested this issue on a development release
044c766
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 0
- 平均合併
- 17 小時 25 分鐘
- 30 天內合併 PR
- 11
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
NanoForge-dev/Loader 的其他 Issue
-
app:client app:website enhancement refactor
難度 2/5 1-3 小時 新手友好度 72/100
NanoForge-dev/Loader#145 ·
維護者通常 1 天內回覆
-
chore(loader-client,loader-server): package.json entry points name files the build does not produce未關閉app:client app:server bug chore good first issue
難度 2/5 1-3 小時 新手友好度 78/100
NanoForge-dev/Loader#144 ·
維護者通常 1 天內回覆
-
app:website bug good first issue
難度 2/5 1-3 小時 新手友好度 85/100
NanoForge-dev/Loader#141 ·
維護者通常 1 天內回覆
-
app:website bug good first issue
難度 2/5 1-3 小時 新手友好度 82/100
NanoForge-dev/Loader#140 ·
維護者通常 1 天內回覆
-
app:server bug
難度 2/5 1-3 小時 新手友好度 85/100
NanoForge-dev/Loader#138 ·
維護者通常 1 天內回覆
查看 NanoForge-dev/Loader 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
難度 1/5 1-3 小時 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
難度 2/5 1-3 小時 新手友好度 79/100
維護者通常 1 天內回覆
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
難度 2/5 1-3 小時 新手友好度 65/100
growilabs/growi#12246 · 3 則留言 ·
維護者通常 1 天內回覆
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 則留言 ·
維護者通常 1 天內回覆