Audit at restore time must not throw and fail the operation #13085
Labels
Area:NuGetAudit
Category:Quality Week
Issues that should be considered for quality week
Functionality:Restore
Priority:2
Issues for the current backlog.
Tenet:Reliability
Crashes, hangs etc.
Type:Bug
Milestone
Found this in an activity log:
If you follow the stack trace, you'll see that the throw is happening in restore command project level and throwing all the way to the solution restore job.
I think the original idea behind this was a warning NU1900, https://learn.microsoft.com/en-us/nuget/reference/errors-and-warnings/nu1900, but we should consider whether need to differentiate between a source being inaccessible altogether and a source not supporting vulnerabilities.
IMO, we should not log a warning if we can't access the feed altogether, as that'd be surfaced by other means potentially, but that would break some scenarios, so maybe we log a min message instead in that case?
We should log an NU1900 warning if the source has vulnerabilities and they're broken for any reason.
cc @zivkan thoughts?
The text was updated successfully, but these errors were encountered: