Why steps is `i32`?

I have many tasks which progresses way beyond i32 and they're always integer. Could you please modify limits? And what's the reason it's have a sign?

and why do you have update so low precision of `f32` for an update? I understand that final result doesn't require greater precision, but it's harder to calculate progress.

For example, I'm downloading 50GB file, on 100Mb/s network, thus I have at most 12 megabytes of per second. Let's say I've downloaded a chunk of 10 megabytes, so if I divide 50 gigabytes to 10 megabytes, I'll have roughly 0, beyond 6th significant digit of `f32`.

If I have greater initial values or lower speed, I'll have 0 progress.

If the progress bar would have `u64` inside of total and `u64` of progress, no such error would occur

Locate the progress-bar implementation and inspect how `steps`, `total`, and update progress are represented and calculated. Compare the current signed `i32` and `f32` choices with the reported large-download case, then define tests that cover large totals and small progress increments; done means those values remain representable and progress updates do not collapse to zero.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.