Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

gracefulKill is a no-op on Windows: node-pty kill(signal) throws and is swallowed

未关闭
#984 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
62/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
typescript, vscode
领域
cli

调研方向

Start in standalone/sidecar/pty-core.js at pty:gracefulKill, then trace the VS Code deactivate path that calls gracefulKill. Reproduce the Windows behavior with a fake node-pty whose kill(signal) throws, and add coverage for both affected hosts. Done means Windows shutdown sends a graceful stop, avoids swallowing the failure, and does not wait the full two-second timeout before exit.

由索引模型根据 Issue 内容生成。

描述

Found during review of #983 (standalone/sidecar/pty-core.js gracefulKill).

On Windows, node-pty's kill(signal) throws for a signal argument. gracefulKill wraps it in a try/catch that swallows the error, so no PTY receives a graceful stop. The function then polls for the full timeout (2 s) before the hard kill. Both hosts are affected: standalone (pty:gracefulKill) and VS Code (gracefulKill on deactivate).

Effect: on Windows, quit and deactivate always wait out the grace period, and shells never get a chance to flush or save history.

Likely fix: on Windows, use the ConPTY close path or send Ctrl+C / Ctrl+Break through the console instead of kill(signal). Then shorten the wait to the actual exit. A test with a fake node-pty whose kill(signal) throws should go red on main.

🤖 Generated with Claude Code

主要语言
TypeScript
星标
5
派生
1
平均合并
11 小时 51 分钟
30 天内合并 PR
341

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

diffplug/dormouse 的其他 Issue

查看 diffplug/dormouse 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。