Copilot CLI in windows fails to start without any output
- 主要語言
- Shell
- 星號
- 11.2k
- 分支
- 1.9k
- 平均合併
- 14 小時 16 分鐘
- 30 天內合併 PR
- 6
描述
### Describe the bug
I was just able to load copilot cli using the "copilot" command. I had a pending update, which I took using /update. And then the cli has not been loading. The "copilot" command fails to do anything, just returns a 0 exit code.
I tried downgrading to the previous version, but the behavior seems to be the same.
### Update:
Installing copilot cli with npm and then running: node "C:\Users\###AppData\Roaming\npm\node_modules\@github\copilot\index.js" works. But the "copilot" command doesn't work.
### Affected version
_No response_
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
貢獻指南
研究方向
先在使用 `/update` 後,以 `copilot` 命令重現 Windows 錯誤,然後將其與直接執行 `node \"C:\\Users\\###AppData\\Roaming\\npm\\node_modules\\@github\\copilot\\index.js\"` 進行比較。追蹤命令的解析方式,並將完成定義為 `copilot` 命令正常啟動並產生預期輸出。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- node.js, shell
- 領域
- cli, operating-systems
- Issue 類型
- 缺陷
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 活躍度
- 冷清
- 描述清晰度
- 需要釐清
- 新手友好度
- 38/100