High frequency error reporting: [error] [default] Error sending telemetry AbortError: The operation was aborted.

[ibelifly]

Select Topic Area

Question

Body

My copilot always reports a high-frequency error, almost every few minutes, which makes it difficult for me to use it smoothly.

2024-07-03 17:03:50.288 [error] [default] Error sending telemetry AbortError: The operation was aborted.
at fetch (c:\Users\user.vscode\extensions\github.copilot-1.208.965\node_modules@adobe\helix-fetch\src\fetch\index.js:96:13)
at cachingFetch (c:\Users\user.vscode\extensions\github.copilot-1.208.965\node_modules@adobe\helix-fetch\src\fetch\index.js:288:16)
at Dq.fetch (c:\Users\user.vscode\extensions\github.copilot-1.208.965\lib\src\network\helix.ts:88:22) {
type: 'aborted',
_name: 'AbortError'
}

I was able to get the copilot to work normally for a short time by restarting the plugin. But within a few minutes, it reported this error again. And sometimes code prompts can be performed normally, but chat cannot be performed, or chat can be performed normally, but code prompts cannot be used. The same thing is that it is all due to the above error report.

[mtobin-tdab]

Has anyone got it working again after this? Been down for me for 3 days

[kiranj26]

Hey @ibelifly,

It sounds like you're experiencing frequent AbortError issues with Copilot's telemetry. Here’s a troubleshooting approach:

1. Restart Copilot:
   Sometimes a restart can temporarily fix the issue.

   Restart the plugin:

   1. Go to Extensions in VSCode.
   2. Disable and then re-enable the GitHub Copilot extension.

2. Update VSCode and Extensions:
   Ensure both VSCode and Copilot extensions are up-to-date.

   Check for updates:

   1. Open Command Palette (Ctrl+Shift+P).
   2. Select Extensions: Check for Updates.

3. Check Network Settings:
   Ensure there are no network issues blocking Copilot's telemetry.

4. Review Logs:
   Look at the logs for more detailed error messages.

If the problem persists, consider reporting it to the GitHub Copilot support team with the detailed error logs.

Let me know if this helps or if you need more assistance!