NuGet should refresh its HTTP cache if it can't find the package requested
We see restore failures when we update a project to consume a package that was just published. We can use `--no-cache` to workaround it, but that shouldn't be necessary. It seems like NuGet should realize it is running from a cache, and attempt to refresh that cache, before failing the restore because it cannot find the package. This would still let the common case be fast while not failing in the case that the cache was stale.
Posted by ericstj on Jul 12, 2016, 7:02 PM
Tags
Related issues
- struct's lifetime requirements can be bypassed via covariant field assignment
- Proposal to Reorganize the Moderation Team and Review Moderation Policies
- Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
- proposal: container/...: generic collection types
- Better Custom Endpoint BYOK
- A concrete policy for backward compatibility until Godot 5.0
Raise real-world problems, find people facing the same issue, and discuss solutions.5,000 issues0 comments
github (Other)
struct's lifetime requirements can be bypassed via covariant field assignment
Proposal to Reorganize the Moderation Team and Review Moderation Policies
Progressive FPS degradation appears to be related to dota2.com — blocking the domain prevents the performance loss
proposal: container/...: generic collection types
Better Custom Endpoint BYOK
A concrete policy for backward compatibility until Godot 5.0
New MTP models not supported
Tracking: 429 / Capacity Issues
NuGet should refresh its HTTP cache if it can't find the package requested
We see restore failures when we update a project to consume a package that was just published. We can use `--no-cache` to workaround it, but that shouldn't be necessary. It seems like NuGet should realize it is running from a cache, and attempt to refresh that cache, before failing the restore because it cannot find the package. This would still let the common case be fast while not failing in the case that the cache was stale.
Comments (0)
No comments yet. Start the discussion.