Mac m1 Sonoma - FSautocomplete not working about fsautocomplete HOT 7 OPEN

This is is pretty fundamental protocol-level wrongness, and I think we should crash as a result. There's a difference between well-formed messages that are missing protocol level fields, and not even having well-formed messages.

from fsautocomplete.

Separately, the StreamJsonRpc library has had several revisions ahead of our current version, and the error messages for header parsing have gotten more clear. If we update users might have more of a clear signal about which component is going wrong here.

from fsautocomplete.

FWIW, tested it just yesterday on the fresh m2, worked quite well. Not sure what's the difference.

from fsautocomplete.

I think this is all runtime related as we've had a few issues pop up that seem to be m1 specific:

• #939
• dotnet/sdk#23267 (comment)
• https://github.com/dotnet/sdk/issues?q=is%3Aissue+is%3Aopen+m1

Not sure if we can do anything about it since it seems runtime related. Nor do I have an m1 macbook to test these things.

from fsautocomplete.

Haven't had my ☕ but looking at the logs, this seems like a normal error if fsautocomplete doesn't receive the correct input. Which editor are you using with fsautocomplete?

from fsautocomplete.

This looks awfully similar to #1109

I would assume replit uses some derivative of vscode/vscodium?

from fsautocomplete.

@baronfel i guess this is another case of "should we crash if we get bad data from a client?". Not sure how to gauge this one.

from fsautocomplete.