You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[18:05:30 DBG] event: (textDocument/publishDiagnostics, { Uri =
"file:///Users/chethusk/oss/FsAutoComplete/test/FsAutoComplete.Tests.Lsp/TestCases/Tooltips/Script.fsx"
Diagnostics =
[|{ Range = { Start = { Line = 0
Character = 0 }
End = { Line = 0
Character = 0 } }
Severity = Some Error
Code = Some "84"
Source = "F# Compiler"
Message =
"Assembly reference 'System.Runtime.Remoting.dll' was not found or is invalid"
RelatedInformation = Some [||]
Tags = None };
{ Range = { Start = { Line = 0
Character = 0 }
End = { Line = 0
Character = 0 } }
Severity = Some Error
Code = Some "84"
Source = "F# Compiler"
Message =
"Assembly reference 'System.Runtime.Serialization.Formatters.Soap.dll' was not found or is invalid"
RelatedInformation = Some [||]
Tags = None };
{ Range = { Start = { Line = 0
Character = 0 }
End = { Line = 0
Character = 0 } }
Severity = Some Error
Code = Some "84"
Source = "F# Compiler"
Message =
"Assembly reference 'System.Web.Services.dll' was not found or is invalid"
RelatedInformation = Some [||]
Tags = None };
{ Range = { Start = { Line = 0
Character = 0 }
End = { Line = 0
Character = 0 } }
Severity = Some Error
Code = Some "84"
Source = "F# Compiler"
Message =
"Assembly reference 'System.Windows.Forms.dll' was not found or is invalid"
RelatedInformation = Some [||]
Tags = None }|] }) <LSPTests>
So the gist is that something in the compiler/FSI typechecking is including those somehow?
We should be able to filter out these erroneous references (they are cosmetic only) but after we do that short-term fix we should report upstream. Also will need to validate this after updating to FCS 33.
The text was updated successfully, but these errors were encountered:
These are definitely related to some stuff upstream in the compiler. These errors end up in the 'unresolvedreferencesset', which is populated only from the 'load closure' of the script.
The set of references seems to be ok now, but for some reason we have 4 spurious references that are sneaking in somehow:
The list of references we include now
The parse errors we get
So the gist is that something in the compiler/FSI typechecking is including those somehow?
We should be able to filter out these erroneous references (they are cosmetic only) but after we do that short-term fix we should report upstream. Also will need to validate this after updating to FCS 33.
The text was updated successfully, but these errors were encountered: