-
Notifications
You must be signed in to change notification settings - Fork 37
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
Errors with .fsx files #29
Comments
It would be super helpful if you could make a minimal example that reproduces the problem. |
@georgewfraser Output from "F# Language Server":
|
Same Problem here. Creating the missing 'assembly' path seems to solve the issue. |
Same issue here, clean install and open up an fsx. |
I think this is windows-specific so I am having trouble reproducing it. Assuming this is only affecting .fsx files, the root of the problem is probably in the function that infers compiler options for .fsx files: It would help to figure this out if someone posted the entire log. |
Log is here: If you have a look at the stack trace, you see that that there is a Problem inside here: It seems that the internal SimulatedMSBuildReferenceResolver is assuming the existence of the mentioned and missing 'assembly' folder. Unfortunately, the stack trace ends there and I cannot see the original Code invoking it. Maybe it's the piece of Code you cited above. Is there a way of Debugging the language Server? Maybe starting it out of VS with a Debugger attached and send a specific stdin to it? |
Yes you should be able to attach a debugger. You can change the command that is used to launch fsharp-language-server right here: Then hit F5 in vscode to run the extension out of your working directory. Then attach to the running process. |
Still can't reproduce this on Mac, unfortunately : ( Give the stack trace, this looks a bit like a problem originating in FSharp.Compiler.Service. @ronaldschlenker you might be able to reproduce this without fsharp-language-server by creating FSharp.Compiler.Service with the options:
|
I try starting with it today... |
The other option is to just add the missing path |
Finally, I am able to reproduce the issue in the Debugger, @georgewfraser. Next step is to create a project where I can isolate the issue. In the meanwhile, your suggested workaround seems reasonable to have a working build on Windows until the root cause is identified. I continue working on it... |
Would someone on this thread please clean-install the latest version 0.1.22 and confirm that the workaround is effective? |
I can confirm it, executing the following steps (VSCode + Windows):
Result:
|
@georgewfraser I think I found the issue, and it's something that should be fixed inside FSharp.Compiler.Service. I raised this issue: dotnet/fsharp#6161 I don't see a possibility this can be fixed here. |
Thanks @ronaldschlenker ! Hopefully the dumb workaround where we add the missing folder will fix this for now. |
Tried to work with FAKE script.
The text was updated successfully, but these errors were encountered: