-
Notifications
You must be signed in to change notification settings - Fork 166
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
Cannot resolve dependency to assembly because it has not been preloaded #631
Comments
I don't know what this is sorry, it might be an OmniSharp-roslyn issue, perhaps try to ask there? I'd recommend getting a raw OmniSharp-roslyn log, by starting the server directly from the command line: cd /Users/frarees/Desktop/test/
/Users/frarees/.cache/omnisharp-vim/omnisharp-roslyn/run -l debug |
Cool, will try sharing there. More insights from the OmniSharp-roslyn log.
Also:
|
Yeah that |
I've seen that the NullReferenceException is happening on other projects that I can open successfully, so might not be related. Aside, since I get more than 3 errors (4
Maybe there's a way to gracefully ignore these? The project actually loads, so I'm wondering if omnisharp-vim is stopping cause it's getting these unknown errors, but could actually continue to function.
|
Hmm, you may be right about that. Do you want to test this out? You could try changing the |
Indeed, it worked! |
Well, just increasing that limit is a pretty simple fix. I don't know what a sensible number of json errors to receive is? I do still want to have this test, as it is a reasonably reliable way to detect that the user is using the HTTP version of the server. Or perhaps instead of just counting invalid json messages from the server, we could count both valid and invalid, and just check that there are more valid than invalid messages. That seems a bit more robust. |
Sounds like a good idea. I guess a message being valid is a greater indicator than a message being invalid. Is it easy to have successful messages when missmatching stdio/http? If it's not easy, what about waiting for n messages and check how many of them are successful? e.g. wait until you get 6 messages, check that 3 of them are valid. |
@frarees could you give the latest version a try? |
All good 👍 |
Log:
It happens just on one of my projects, and I cannot seem to figure out where this comes from. Any clue? Thanks!
The text was updated successfully, but these errors were encountered: