Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

v7.21.0 is causing intellisense issues in VS code #2035

Open
fwaris opened this issue Aug 19, 2024 · 12 comments · Fixed by dotnet/fsharp#17565
Open

v7.21.0 is causing intellisense issues in VS code #2035

fwaris opened this issue Aug 19, 2024 · 12 comments · Fixed by dotnet/fsharp#17565
Labels
bug upstream - FCS issue Changes that require changes to FCS to complete

Comments

@fwaris
Copy link

fwaris commented Aug 19, 2024

Just upgraded to v7.21.0.

Seeing red squiggles in files that should compile fine.
Hovering over a squiggle gives 'index out of bounds' error message.

Fixed by going back to v7.20.3

Running Window 11 with the following sdks installed

C:\Users\Faisa>dotnet --list-sdks
6.0.416 [C:\Program Files\dotnet\sdk]
8.0.301 [C:\Program Files\dotnet\sdk]
8.0.400 [C:\Program Files\dotnet\sdk]
@vzarytovskii
Copy link

A stacktrace would be helpful, to understand if it happens in FSAC or FCS.

@vzarytovskii
Copy link

vzarytovskii commented Aug 20, 2024

This is how it looks:
telegram-cloud-photo-size-2-5343543798967429993-y

And also this:
telegram-cloud-photo-size-2-5343543798967429995-y

I have no stacktrace at this point.

@kant2002
Copy link
Contributor

For the record. There no logs anywhere to be found. Even after enabling

"FSharp.verboseLogging": true,
"FSharp.trace.server": "verbose",

It appear to me when developing using Oxpecker library, and when I modify computation expression. It's hard to reproduce for now. so does computatoin expression is the culprit is speculative.

@vzarytovskii
Copy link

Likely suspect is https://github.com/dotnet/fsharp/pull/17096/files which uses HashMultiMap as an underlying structure, which is not threadsafe.

@fwaris
Copy link
Author

fwaris commented Sep 17, 2024

With the latest version -v7.21.1 - there are some issues still remaining - prob. related to the same fix.

When I edit a file, sometimes I get red squiggles.
The error is (when hovering over the squiggles):

internal error: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct. F# Compiler[193](https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/compiler-messages/fs0193)

@vzarytovskii
Copy link

vzarytovskii commented Sep 17, 2024

With the latest version -v7.21.1 - there are some issues still remaining - prob. related to the same fix.

When I edit a file, sometimes I get red squiggles.

The error is (when hovering over the squiggles):


internal error: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct. F# Compiler[193](https://docs.microsoft.com/en-us/dotnet/fsharp/language-reference/compiler-messages/fs0193)

This should've been fixed in FCS already. Are there any examples of code, or stack trace?

@TheAngryByrd
Copy link
Member

This should've been fixed in FCS already

@vzarytovskii was this released in a nuget package yet?

@baronfel
Copy link
Contributor

We're using the 8.0.400 build - did the fix come out after?

@vzarytovskii
Copy link

vzarytovskii commented Sep 17, 2024

We're using the 8.0.400 build - did the fix come out after?

Yes, not in 8 branch though, we didn't backport it there

@baronfel
Copy link
Contributor

Ok, so FSAC updating to https://www.nuget.org/packages/FSharp.Compiler.Service/43.9.100-preview.24422.2 or similar should unblock this.

@baronfel
Copy link
Contributor

I suppose now that RC1 is out we should probably look at doing this anyway.

@vzarytovskii
Copy link

Yeah, there are whole bunch of fixes there. Should be fine despite it being a "preview".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug upstream - FCS issue Changes that require changes to FCS to complete
Projects
None yet
Development

Successfully merging a pull request may close this issue.

5 participants