Copilot in Windows + WSL + VSCode: sometimes doesn't work, sometimes works fine, I don't get it. #29269
Replies: 13 comments 18 replies
-
@JoannaFalkowska I'm sorry you're having difficulties. Can you please paste the relevant parts of View -> Output; select GitHub Copilot from the pulldown. |
Beta Was this translation helpful? Give feedback.
-
This is STILL unresolved, I'm STILL struggling with the same problem, without any idea why does it happen. On good days, I open my WSL files in VSCode and Copilot instantly works like a charm, swiftly returning completions all day. On bad days, in exactly the same setting, it returns no completions, or manages to do so only for isolated very simple files, while completely blanking and timing out when asked for completions inside a complicated TS repo. It's frankly ridiculous, completely unreliable, deciding to work or not work without any rhyme or reason. I'd like to understand at least why and whether I can do anything to help it function properly. Because as it is now, it's a paid feature working in a way that can hardly be considered out of beta. |
Beta Was this translation helpful? Give feedback.
-
This happens to me as well. I recently formatted my pc and installed the latest windows 10 pro.
The Copilot log does not show any error as @JoannaFalkowska mentioned when I try to get any suggestion from Copilot.
But, If I waited long enough, it does return with the timout error. This is the list that I have tried
I am not sure what is going on. I will update the post if I figure out the solution. |
Beta Was this translation helpful? Give feedback.
-
Alright, it has been almost a month since I posted. I do not have the exact solution, but I kinda know what is the problem. So, Copilot does use multiple servers to get responses, but the problem is once Copilot connected to a server, it does not get changed even if the connection gets timed out. I am not sure why Copilot does not automatically change the connection server. But, I think sometimes the copilot server thinks some connection from "WSL" is evil, so they block the IP address for a short period time. This is why we experience such cases. The workaround is using a VPN. Since the communication between your IP and the Copilot server is not established, you need to changed your IP address. |
Beta Was this translation helpful? Give feedback.
-
Hey, |
Beta Was this translation helpful? Give feedback.
-
Interesting. My issue may be slightly different. The curl won't return anything on WSL2, while it returns OK on windows. Any suggestions? |
Beta Was this translation helpful? Give feedback.
-
Here's how I set up squid proxy with docker for a workaround: squid.conf
run.sh
Dockerfile
build.sh
then set http://0.0.0.0:3128 as your proxy in vscode. NOTE: I have to remove the proxy when installing/updating extentions |
Beta Was this translation helpful? Give feedback.
-
This shitty issue still hasn't been resolved lol |
Beta Was this translation helpful? Give feedback.
-
Same issue here |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
Same issue |
Beta Was this translation helpful? Give feedback.
-
[SOLVED] Downgrade to version v1.188.0 Problem: There is an issue in the latest version of Github Copilot that causes it to work on Windows but not WSL. |
Beta Was this translation helpful? Give feedback.
-
It worked fine for months, but now it suddenly stopped.
When I open a VSCode window in "vanilla" Windows, Copilot works completely fine, i.e. I can create a new file and it starts giving me suggestions as expected.
However when I open a VSCode window in WSL, Copilot extension manages to start up and authenticate, but then it gets stuck on "Synthesizing 0/10 solutions". I can see no errors in the console. It's just stuck.
I tried:
seahorse
)seahorse
) and re-authenticating GithubNone of those helped, and I'm completely lost as to why Copilot is suddenly unable to cooperate with my WSL. I don't use any VPN, and haven't changed any settings this past week.
I'd appreciate any kind of pointers as to how I could debug this.
Beta Was this translation helpful? Give feedback.
All reactions