-
Notifications
You must be signed in to change notification settings - Fork 420
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
OmniSharp-Roslyn v1.32.2+ HTTP is refusing connections #1274
Comments
I had been meaning to try to debug this, or at least bisect to find the exact commit that causes problems, but I ran into the issue of not being able to build OmniSharp-roslyn on my archlinux machines. After some fiddling with GitVersion and making a couple of changes to However ... my build of the latest version works in vim! And so does a build of So as far as I can tell at this stage, the problem has something to do with the actual compiled releases, not the code itself? |
Until OmniSharp/omnisharp-roslyn#1274 is resolved, `:OmniSharpInstall` with no arguments will install version v1.32.1 Closes #393, #410
@nickspoons this is on archlinux? That's really odd... everything shipped with the releases is built on Travis and shipped from there. Is there something about them being built on an ubuntu system that might cause issues? |
@david-driscoll the issue is occurring on all *nix's, including Ubuntu, see the issue description. I've experienced it in an archlinux VM, and an archlinux flavoured WSL. |
Any update or progress on this? |
I can confirm that manually building the latest source from git on Arch Linux (following @nickspoons modifications to the build scripts) results in a working build of the HTTP driver, whereas installing any compiled release after version 1.32.1 from here gives me a broken build that refuses connections.
|
Maybe Eureka.
rm -Rf ~/.omnisharp
cd ~/Downloads
wget https://github.com/OmniSharp/omnisharp-roslyn/releases/download/v1.32.8/omnisharp.http-linux-x64.tar.gz
mkdir -p ~/.omnisharp/omnisharp-roslyn
tar -xvzf ~/Downloads/omnisharp.http-linux-x64.tar.gz -C ~/.omnisharp/omnisharp-roslyn Thanks the command :
you could see that there is nothing diff between this two folders. Therefore, the folder used for the release is
Or
you could see there are missing files in the published version, especially
You could see that the released version works ! ( Therefore, why in I'm a student, therefore I'm very beginner in c#. Hard to me to find any solution. But I think it could be very simple to find a solution ! |
Eureka. It seems to delete in build.cake void DeleteUnnecessaryAssemblies(string folder)
{
FileHelper.Delete(CombinePaths(folder, "System.AppContext.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Numerics.Vectors.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Runtime.InteropServices.RuntimeInformation.dll"));
FileHelper.Delete(CombinePaths(folder, "System.ComponentModel.Primitives.dll"));
FileHelper.Delete(CombinePaths(folder, "System.ComponentModel.TypeConverter.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Console.dll"));
FileHelper.Delete(CombinePaths(folder, "System.IO.FileSystem.Primitives.dll"));
FileHelper.Delete(CombinePaths(folder, "System.IO.FileSystem.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Security.Cryptography.Encoding.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Security.Cryptography.Primitives.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Security.Cryptography.X509Certificates.dll"));
FileHelper.Delete(CombinePaths(folder, "System.Threading.Thread.dll"));
} I make a PR |
Contrary to the hypothesis make above, the error is not caused by Travis. Therefore I have done a I've found:
|
I hope it will help to merge #1361 :-) |
Any indications on when this issue may be fixed? OmniSharp is unusable for me on vim without this since I have projects referencing each other. |
@satiani Even if this is fixed, will you still have confidence in a project that left Linux users high and dry for months on end? |
@ohjames It's an open source project run by volunteers. If you can't make the time to help fix this issue, then at least avoid negative comments. |
@satiani The issue has been fixed but nobody is listening. Just because people are volunteering their time doesn't make them immune to criticism. Had plenty of criticism on some of my own open source projects from time to time and when it's deserved I'm thankful that somebody booted me into action. |
constructive criticism != cynicism |
Fix refusing HTTP connections ( #1274 )
As @david-driscoll as merged #1361 (thanks 😄 ) this issue could be closed 😄 |
@rchande @nickspoons maybe it could be cool to make a new release now for vim users ? |
@JulioJu might as well wait for a release so we can test it, before closing this issue? (I don't have any control over releases, I'm just an OmniSharp-vim maintainer) |
You can already test it by grabbing the pre-release using these instructions https://github.com/OmniSharp/omnisharp-roslyn#prerelease-versions In the project, we have the approach that issues are closed as soon as the fix is merged (not when it's released). Feel free to open a new one (or reopen this one) when you still have problems with the prerelease - thanks! |
The Problem
The OmniSharp-Roslyn HTTP (v1.32.2) server is refusing all HTTP connections.
The problem seems to have occurred between v1.32.1 and v1.32.2.
Systems this occurs on
This issue has been reported to occur on these devices:
It does not occur on the Windows versions of the builds.
Running v1.32.2 of the server from the command line
This was run with the
-v
flag, the previous version of the server printed thousands of lines ofdebug:
data, whereas v1.32.2 did not.Click to view output.
OmniSharp-vim log:
OmniSharp-vim is unable to connect to v1.32.2 of the OmniSharp-Roslyn server, this is the error log produced.
NOTE: This does not seem to be an issue with OmniSharp-vim.
Click to view output.
Visiting the server in a web browser
Obviously you aren't meant to use OmniSharp from a web browser, but the responses do highlight a difference between the two versions of the server.
v.32.1
A blank web page is displayed and the server prints some connection info to STDOUT.
v.32.2
Nothing is printed to STDOUT, but the browser displays this error message:
If any more information is needed, please let me know. 😄
Edit: Add more affected systems.
The text was updated successfully, but these errors were encountered: