You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In #120562, @DilumAluthge indicated that it's expected/acceptable for the conservative registry flavor to lag up to 24 hours. I think it would provide a better package developer and user experience if we limited that lag to a lower time (ideally minutes or seconds) and document expected lag time.
One possible way to do this would be to eliminate conservative altogether and make the package servers capable of serving packages they haven't fully downloaded yet by streaming from their source (e.g. GitHub) with caching and prioritizing such streaming over traffic to those source servers that is for updating packages that don't have users actively waiting for them.
The text was updated successfully, but these errors were encountered:
In #120562, @DilumAluthge indicated that it's expected/acceptable for the
conservative
registry flavor to lag up to 24 hours. I think it would provide a better package developer and user experience if we limited that lag to a lower time (ideally minutes or seconds) and document expected lag time.One possible way to do this would be to eliminate
conservative
altogether and make the package servers capable of serving packages they haven't fully downloaded yet by streaming from their source (e.g. GitHub) with caching and prioritizing such streaming over traffic to those source servers that is for updating packages that don't have users actively waiting for them.The text was updated successfully, but these errors were encountered: