Description
openedon Jul 3, 2022
Problem
From original thread https://internals.rust-lang.org/t/call-for-testing-cargo-sparse-registry/16862/20?u=pickfire
One thing I noticed is that the fetching need to go through several loops now, previously it just fetch until 100% then done, but now when it reached 100%, then it had to fetch another time again, and the total stuff needed to fetch which keeps increasing (1 -> 10 -> 50 -> 100 -> 130) resulting in the progress decreasing, feels weird.
I feel like the total should be - until there is a definite answer to the total number that needs to fetch then only show it rather than keep increasing it.
Steps
rustup update nightly
cargo +nightly -Z sparse-registry update
Possible Solution(s)
A way to improve that in the registry would be to on publish, provide an optional
expected_dep_forest_size
from the number of transitive dependencies used at publish time. This number could be used to provide a reasonable progress estimate quickly.
Notes
No response
Version
No response