[Help Wanted]: LanguageServerProtocol.ServerError 8

[mikeswanson]

Before Reporting

• I have checked FAQ, and there is no solution to my issue
• I have searched the existing issues, and there is no existing issue for my issue

Describe your issue

Until a week or two ago, I had been using Copilot for Xcode without any issues. However, at some point, suggestions just stopped (even Editor/Copilot/Get Suggestions doesn't work).

I've completely uninstalled and re-installed the app, double- and triple-checked permissions, re-installed the language server, signed out and back in multiple times, rebooted multiple times, and much more. I've been at this for many hours today.

Yes, I have a Copilot subscription on GitHub, and indeed, it's still active. In fact, Visual Studio Code on the same machine shows suggestions just fine using the same GitHub account.

The language server shows Copilot.Vim v1.25.0, language server version is 1.94.0, and its status is "OK". On occasion, when I switch away from the Service tab and back, I see a red "The operation couldn't be completed. (LanguageServerProtocol.ServerError 8.)" message.

When I look at the Console log, the only lines that stand out are:

error	16:02:23.026664-0700	CopilotForXcodeExtensionService	stderr: [ERROR] [default] [2024-04-05T23:02:23.026Z] Request Error: (FetchError) unable to get local issuer certificate
error	16:02:23.028335-0700	CopilotForXcodeExtensionService	stderr: [ERROR] [ghostText] [2024-04-05T23:02:23.028Z] Error on ghost text request: (FetchError) unable to get local issuer certificate

Is anyone familiar with this issue? Or are there local certificates that I might be missing. I've looked through issues, the FAQ, the wiki, and more, and I've come up empty.

[intitni]

Are you using a self-signed certificate for any of the GitHub domain names? You can try the workaround in #455, which imports certificates in your keychain into Node.

[mikeswanson]

I've finally returned to using the Copilot integration, and it seems to be working now (without changing anything, other than an upgrade to the app).

For what it's worth, I am not using any self-signed certificates, which is why this was confusing to me. But, it's resolved itself, so I'll close this issue. Thanks!