-
Notifications
You must be signed in to change notification settings - Fork 473
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
[Workaround found] NuGet errors in Windows build: NU1101 No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages #155
Comments
Been having this issue since Monday (the 14th) at least |
I updated a few of my nuGet packages, build worked, rerun the build, it failed. Hmm. Somesort of caching issue? |
Found the fix, add this before the build (Ofcourse change the bumbo-web stuff to your own projectfolder/name): |
Seems to have worked, thank you kindly. |
Looks like that did the trick, nice one! |
Avoid these errors that recently started appearing in GitHub actions Windows environment: ``` [...] D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1101: Unable to find package Mono.Posix.NETStandard. No packages exist with this id in source(s): Microsoft Visual Studio Offline Packages [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 34D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1102: Unable to find package System.Collections.Immutable with version (>= 1.7.1) [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 35D:\a\elm-fullstack\elm-fullstack\implement\PersistentProcess\PersistentProcess.WebHost\PersistentProcess.WebHost.csproj : error NU1102: - Found 2 version(s) in Microsoft Visual Studio Offline Packages [ Nearest version: 1.2.0 ] [D:\a\elm-fullstack\elm-fullstack\implement\test-elm-fullstack\test-elm-fullstack.csproj] 36Error: Process completed with exit code 1. ``` Integrate the workaround discovered by Jordan Brown, Gewoon Jaap, et al. For context, see: + actions/setup-dotnet#155 + actions/runner-images#1891
by inserting a cleanup step per actions/setup-dotnet#155 (comment).
Use fix from actions/setup-dotnet#155
Yes that works. Thank you @GGG-KILLER ! |
@jasonleenaylor, also you can try this step as workaround:
|
See actions/setup-dotnet#155 (comment) for more details.
- borrowed from actions/setup-dotnet#155
* Workaround for build error - borrowed from actions/setup-dotnet#155
…the Windows images being used to build. More information in this thread: actions/setup-dotnet#155 (comment)
Fixes flakiness in Windows build See actions/setup-dotnet#155
Description
I recently started getting failures in the Windows build for the dotnet action of my project, see https://github.com/csinkers/ualbion/runs/1574151895
Linux and macOS are still working fine, no project files / NuGet configurations have been changed since the last successful build. Sounds like it's only looking for locally cached packages rather than using nuget.org.
Details
Yaml:
Platform: windows-latest
Version: .NET Core 3.1.100
Action link: https://github.com/csinkers/ualbion/actions
Error messages:
Was this a regression from previous behavior? – Yes
The text was updated successfully, but these errors were encountered: