-
Notifications
You must be signed in to change notification settings - Fork 790
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
error NU1301: Unable to load the service index for source https://api.nuget.org/v3/index.json (in VS .fsx editor or FSI) #16278
Comments
Is there a way to look at what nuget.exe is doing, like a log file, or the terminal output of it? |
@forki are you up for hire to help the nuget & packaging design team to push nuget forward? |
Nothing to do with dependency manager, it uses nuget to restore packages |
@vzarytovskii do you recommend I post the same issue on nuget repository? |
I think so, yes |
ok, makes sense; is there still a sense that the package extension could surface diagnostic in FSI output? I believe it is shelling out to msbuild, which shells to nuget, so there could be stuff that occur and need to be printed to the user for better diagnosis. |
I'm facing this when using the
#r "nuget: ..."
FSI extension in VS or fromFsiAnyCpu.exe
(and likely indotnet fsi
the same):Repro steps
Editing a .fsx script with few
#r "nuget: ..."
, the first one shows squiggles with this error message, which also shows in the VS status bar.Expected behavior
In case of network error, I think it needs to gracefully attempt package resolution based on ~/.nuget/packages, and report the network issues via telemetry, and fail to the user only if the local resolution failed.
Maybe there is a way to show a warning rather than an error squiggle in such case.
It may still be allowed to fail if it can't resolve dependencies based on the local cache.
Actual behavior
Type checking really goes haywire with difficult to troubleshoot errors based on what you use (type providers) when evaluating the script or inspecting in the tooling.
Known workarounds
Related information
I never face this with machine in US, but do in Europe.
possibly related issue: NuGet/NuGetGallery#9396 (comment)
VS 2022 Version 17.7.6
The text was updated successfully, but these errors were encountered: