Copilot cannot launch from WSL after upgrading to `1.0.64` from PowerShell
- Vorherrschende Sprache
- Shell
- Sterne
- 11.2k
- Forks
- 1.9k
- Ø Merge
- 14 Std. 16 Min.
- Gemergte PRs (30 T.)
- 6
Beschreibung
### Describe the bug
I use GitHub Copilot in both Windows (from PowerShell) and WSL.
This morning I updated the Windows installation to `1.0.64`. The Windows version is working fine after the update.
However, the WSL installation cannot launch. The error message is
```bash
$ copilot
Failed to load package index: /home/shengjiema/.cache/copilot/pkg/linux-x64/1.0.64-1/index.js SyntaxError: Invalid or unexpected token
at compileSourceTextModule (node:internal/modules/esm/utils:318:16)
at ModuleLoader.moduleStrategy (node:internal/modules/esm/translators:90:18)
at #translate (node:internal/modules/esm/loader:435:20)
at afterLoad (node:internal/modules/esm/loader:491:29)
at ModuleLoader.loadAndTranslate (node:internal/modules/esm/loader:496:12)
at #getOrCreateModuleJobAfterResolve (node:internal/modules/esm/loader:549:36)
at afterResolve (node:internal/modules/esm/loader:597:52)
at ModuleLoader.getOrCreateModuleJob (node:internal/modules/esm/loader:603:12)
at node:internal/modules/esm/loader:622:32
at TracingChannel.tracePromise (node:diagnostics_channel:362:14)
```
### Affected version
`copilot --version` does not work in WSL, but the Windows installation says `GitHub Copilot CLI 1.0.64.`
### Steps to reproduce the behavior
_No response_
### Expected behavior
_No response_
### Additional context
_No response_
Beitragsleitfaden
Rechercherichtung
Beginne damit, `copilot` in WSL mit der Version `1.0.64` zu reproduzieren, und untersuche die im Fehler referenzierte zwischengespeicherte Datei `linux-x64/1.0.64-1/index.js`. Vergleiche das Verhalten von WSL mit der funktionierenden PowerShell-Installation; fertig ist es, wenn `copilot` in WSL startet und `copilot --version` funktioniert.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- node.js, powershell, shell
- Bereich
- cli, operating-systems
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Ruhig
- Klarheit
- Muss geklärt werden
- Anfängerfreundlichkeit
- 35/100