-
-
Notifications
You must be signed in to change notification settings - Fork 883
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
lsp-install-server omnisharp fails on macOS #3734
Comments
@razzmatazz willing to take a look? |
will do! later today or tommorow |
btw, @theschmocker what platform are you on your mac, intel or apple/m1 ? |
Hey @razzmatazz, I'm on an M1 |
I am using the exact same configuration (doom-emacs + 28.2 + m1) so I should be able to replicate this.. UPDATE: yes, it fails for me too.. curiously messages buffer says:
but there appears to be no progress whereas downloading the file via browser works.. |
hmm, when it does succeed to download, starting OmniSharp fails with:
curiously I do have 6.0.8 runtime installed:
wait a minute.. it is trying to run x64 (intel) binary! what the heck.. because the url to dowload contains
|
hmm. the file IS arm64 binary..
what is going on.. forcing the OS to run this as arm64 fails too:
some googling points me to: checking things on my machine:
apparently tried to do this:
and now things started to work somewhat:
lets try reinstalling omnisharp and check if things are better.. |
OK, it seems that this helped to make it work.. downloading the server albeit takes weirdly long time, probably DNS or HTTPS setup takes too long on our emacs build (macos/arm)
which emacs distro are you using @theschmocker, https://github.com/d12frosted/homebrew-emacs-plus ? or something else? |
@razzmatazz I am using https://github.com/d12frosted/homebrew-emacs-plus, installed with options I had a similar issue with OmniSharp and libhostfxr.dylib after installing it manually, but fixed it by setting the DOTNET_ROOT environment variable for my shell like |
hmm. but does it start for you now via command line? (once it gets installed properly) |
It does: ~/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn (master) » cat /etc/dotnet/install_location
/usr/local/share/dotnet/x64
~/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn (master) » cat /etc/dotnet/install_location_arm64
/usr/local/share/dotnet
~/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn (master) » echo "$DOTNET_ROOT"
/usr/local/share/dotnet
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
~/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn (master) » ./OmniSharp
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Stdio.Host","Message":"Starting OmniSharp on Unknown 0.0 (Unknown)"},"Seq":1,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Services.DotNetCliService","Message":"Checking the 'DOTNET_ROOT' environment variable to find a .NET SDK"},"Seq":2,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Services.DotNetCliService","Message":"DotNetPath set to /usr/local/share/dotnet/dotnet"},"Seq":3,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.Discovery.MSBuildLocator","Message":"Located 1 MSBuild instance(s)\n 1: .NET Core SDK 6.0.400 17.3.0 - \"/usr/local/share/dotnet/sdk/6.0.400/\""},"Seq":4,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.Discovery.MSBuildLocator","Message":"Registered MSBuild instance: .NET Core SDK 6.0.400 17.3.0 - \"/usr/local/share/dotnet/sdk/6.0.400/\""},"Seq":5,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0"},"Seq":6,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.MSBuild.ProjectSystem","Message":"No solution files found in '/Users/me/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn'"},"Seq":7,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Script.ScriptProjectSystem","Message":"Detecting CSX files in '/Users/me/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn'."},"Seq":8,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Script.ScriptProjectSystem","Message":"Did not find any CSX files"},"Seq":9,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.WorkspaceInitializer","Message":"Configuration finished."},"Seq":10,"Type":"event"}
{"Event":"log","Body":{"LogLevel":"INFORMATION","Name":"OmniSharp.Stdio.Host","Message":"Omnisharp server running using Stdio at location '/Users/me/.emacs.d/.local/etc/lsp/omnisharp-roslyn/latest/omnisharp-roslyn' on host -1."},"Seq":11,"Type":"event"}
{"Event":"started","Body":null,"Seq":12,"Type":"event"} |
mhm.. so the actual issue you're reporting is slow/broken installation process right? once it is installed it works ok? |
looks like it can get closed right ? |
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
Trying to install omnisharp on macOS fails in 1 of 2 ways:
Steps to reproduce
Attempt to install omnisharp using
M-x lsp-install-server RET omnisharp RET
using Doom Emacs on macOS with Apple SiliconExpected behavior
I would expect the omnisharp-roslyn.zip archive to have been downloaded fully and for the unzipped directory to contain all of the files from the archive.
Which Language Server did you use?
lsp-csharp -- attempting to download omnisharp
OS
MacOS
Error callstack
Anything else?
I'm using Doom with Emacs 28.2 (was an issue on 28.1, as well), but I've unpinned lsp-mode and lsp-ui in order to use the latest versions.
Clojure's LSP is downloaded in the same way, AFAICT. It took quite a while, but eventually completed and worked
The text was updated successfully, but these errors were encountered: