Copilot works for a while then stuck "generating"

[TWeatherston]

Select Topic Area

Bug

Body

I'm having issues using Copilot in VSCode on my Mac. I do not have these same problems on my Linux laptop on the same network.

Everything seems to work fine for 5-10 minutes but then I'll suddenly stop getting any code suggestions and whenever I try to use the chat feature, it just sits at "Generating".

The only fix seems to be restarting VSCode but obviously I don't want to have to do this every 5 minutes!

This is the output from the diagnostics:

- Extension Version: 0.23.2 (prod)
- VS Code: vscode/1.96.1
- OS: Mac

## Network

User Settings:
json
  "github.copilot.advanced.debug.useElectronFetcher": true,
  "github.copilot.advanced.debug.useNodeFetcher": false,
  "github.copilot.advanced.debug.useNodeFetchFetcher": true


Connecting to https://api.github.com:
- DNS ipv4 Lookup: timed out after 10 seconds
- DNS ipv6 Lookup: timed out after 10 seconds
- Proxy URL: None (0 ms)
- Electron fetch (configured): HTTP 200 (161 ms)
- Node.js https: timed out after 10 seconds
- Node.js fetch: timed out after 10 seconds
- Helix fetch: timed out after 10 seconds

Connecting to https://api.githubcopilot.com/_ping:
- DNS ipv4 Lookup: timed out after 10 seconds
- DNS ipv6 Lookup: timed out after 10 seconds
- Proxy URL: None (0 ms)
- Electron fetch (configured): HTTP 200 (340 ms)
- Node.js https: timed out after 10 seconds
- Node.js fetch: timed out after 10 seconds
- Helix fetch: timed out after 10 seconds

The same diagnostics run immediately after opening vscode:

- DNS ipv4 Lookup: 140.82.112.3 (2 ms)
- DNS ipv6 Lookup: ::ffff:140.82.112.3 (21 ms)
- Proxy URL: None (3 ms)
- Electron fetch (configured): HTTP 200 (142 ms)
- Node.js https: HTTP 301 (345 ms)
- Node.js fetch: HTTP 200 (447 ms)
- Helix fetch: HTTP 200 (503 ms)

Connecting to https://api.githubcopilot.com/_ping:
- DNS ipv4 Lookup: 140.82.114.22 (21 ms)
- DNS ipv6 Lookup: ::ffff:140.82.114.22 (2 ms)
- Proxy URL: None (0 ms)
- Electron fetch (configured): HTTP 200 (112 ms)
- Node.js https: HTTP 200 (355 ms)
- Node.js fetch: HTTP 200 (323 ms)
- Helix fetch: HTTP 200 (339 ms)```

Any ideas as to why this would suddenly start timing out?

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐

[akbartaimurr]

i second this, i'm logged into github and copilot but for some reason, its still stuck on generating