VSCodium / vscodium

binary releases of VS Code without MS branding/telemetry/licensing
https://vscodium.com
MIT License
24.29k stars 1.02k forks source link

VSCodium does not recall Copilot sign in on Pop! OS #1846

Open Fulguritude opened 2 months ago

Fulguritude commented 2 months ago

Describe the bug I've installed Copilot according to the guide. It works. I've got my ghu_ creds in my ~/.config/github-copilot/hosts.json, etc. However, every time I re-launch the app, it asks me to sign in to github again.

I also did the "cancel" option while trying to connect, which then suggests for me to use the PAT approach. This approach simply does not work with VS Codium.

I get this:

2024-04-11 22:35:26.373 [info] [auth] Invalid copilot token: missing token: 404 
2024-04-11 22:35:26.387 [info] [auth] Invalid copilot token: missing token: 404 
2024-04-11 22:35:26.390 [error] [auth] Extension activation failed: "User not authorized"

then I retry, and get this

2024-04-11 22:35:49.021 [error] [auth] Retrying auth
2024-04-11 22:36:11.665 [error] [auth] Extension activation failed: "No auth flow succeeded."

Please confirm that this problem is VSCodium-specific

In fact, Microsoft VS Code has a similar, but different bug. It also asks me to sign in every time, but the web sign in (from weird complex github links) doesn't work, however the PAT seems to, so when I do the same "try another method", it immediately realizes that things are actually fine and leaves me be, without trying to launch a browser.

Please confirm that the issue/resolution isn't already documented

The "Sign in to GitHub" section in the index does not solve my problem (unless I misunderstood what I had to do, which I don't exclude).

To Reproduce Steps to reproduce the behavior:

  1. Find a Linux with Pop-OS! (Ubuntu variant) 22.04 installed
  2. Install VS Codium
  3. Follow the steps in the guide (my version of the extension is GitHub.copilot-1.179.816.vsix)
  4. Sign in via the copilot extension notification box (either method: link or PAT)
  5. Close VS Codium
  6. Open VS Codium again

Expected behavior Not being asked to connect every time. Even VS Code's version of the bug (which is 3 quick clicks to resolve, a bit annoying, but much less time-consuming than the 8 hex digit captcha-ish launch for Codium) is an improvement.

Desktop (please complete the following information):