Failed to parse certificate

[aqyuki]

After 256393d, copilot.lua outputs a warning like the following image when it starts. If I fix it to 25ab971 and run copilot.lua, it doesn't output any warnings.
Does anyone know anything about this issue?

[JoseConseco]

same

[AntoineGS]

That first one is (the editorInfo) should now be fixed.
The certificate were likely warnings that were previously not shown (and maybe they should not?) and are now showing due to the new logger.
I might make then a lower level so they do not bother as much, hmm.

[bermeitinger-b]

It depends if they should be shown or not. In my Arch installation, the system certificates have a comment in the first line to indicate the issuer. Ideally, as a user, I generally want to be informed about certificate issues.

Example of /etc/ca-certificates/extracted/ca-bundle.trust.crt

# ACCVRAIZ1
-----BEGIN TRUSTED CERTIFICATE-----
...

This should also be the case in Fedora. At least on Ubuntu, the file with all system certificates is in /etc/ssl/certs/ca-certificates.crt and does not contain any comments.

[AntoineGS]

Yeah that's an issue on the Copilot side, there's an issue opened I believe though I cannot seem to find it now that I want to.
I will make the LSP messages optional and off by default as this is too much of a big change to start flooding everyone with LSP errors, PR incoming.