-
-
Notifications
You must be signed in to change notification settings - Fork 15.4k
roslyn-ls: 4.10.0-2.24124.2 -> 4.12.0-1.24359.11 #318497
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
Conversation
cannot fetch-deps, possible cause? #315574 |
eh, current status: linux - works, darwin - build error, reproducible locally with plain Looks like upstream issue: dotnet/roslyn#73439 A part of our log:
|
Because the fix for darwin build in the upstream repo is nowhere in sight, could we try a different approach here? I have a working example in my personal repo where I install roslyn-ls from the Nuget packages published to this feed - those are official Microsoft builds. This is the same approach that VSCode's C# Dev Kit extension uses to install this server based on: dotnet/roslyn#71474 (comment) @SuperSandro2000 could we have something like that in nixpkgs? It would simplify this package quite a bit, but the downside is that we would rely on binary blobs published to nuget. On the other hand, we already rely on them when downloading nuget dependencies for any dotnet project. FYI: my proposition here: #330683 |
Sounds fine to me |
I seem to be able to work around the stack overflow error by doing this:
However, I haven't tested the resulting binary (other than I was able to track down the stack overflow to a specific csc invocation, and wasn't able to reproduce it using the compiler from the 9.0 preview 6 sdk. I believe the change above will cause it to use the SDK compiler. |
Result of 1 package built:
|
I also built this on darwin, but I had to disable the sandbox due to NixOS/nix#4119. |
Thank you @corngood for the help and fix! I'm building and testing on darwin right now. |
ok, I removed all sdks except for 9_0 - it does not influence deps.nix anymore and the app still builds and works fine. |
Result of 1 package built:
|
Thanks! Looks good to me. Are you happy if I merge it now? |
Have you tested with a project that isn't using SDK 9? I assume so, but I just want to double check that the SDK change doesn't reduce compatibility. |
Result of 1 package built:
|
@corngood now I am ok to merge, as darwin has just built 😄 |
Description of changes
Updating the package.
Added dotnet sdk 9 and removed all other sdks - whether they're present or not, the app compiles and works the same, and the generated deps.nix are also the same.
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.