Copilot CLI in windows fails to start without any output
- Linguagem predominante
- Shell
- Estrelas
- 11.2k
- Forks
- 1.9k
- Merge médio
- 14h 16min
- PRs com merge (30d)
- 6
Descrição
### 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_
Guia de contribuição
Direção de pesquisa
Start by reproducing the Windows failure with the `copilot` command after using `/update`, then compare it with running `node "C:\Users\###AppData\Roaming\npm\node_modules\@github\copilot\index.js"` directly. Trace how the command is resolved and define done as the `copilot` command starting normally and producing its expected output.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Stack de tecnologia
- node.js, shell
- Domínio
- cli, operating-systems
- Tipo de issue
- Bug
- Dificuldade
- 3/5
- Tempo estimado
- 1-2 dias
- Status de atividade
- Pouca atividade
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 38/100