Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings.
Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
It could be a rounding error. Even a single byte short would still mean unrepairable.
However, keep in mind that the check can never be 100.000% accurate.
It's up to you to decide.
Having said that, 100.0% should not have been shown here, precisely because it is unclear.
99.9% should be the maximum number shown.
shypike wrote:It could be a rounding error. Even a single byte short would still mean unrepairable.
However, keep in mind that the check can never be 100.000% accurate.
It's up to you to decide.
Having said that, 100.0% should not have been shown here, precisely because it is unclear.
99.9% should be the maximum number shown.
Kind of what I thought. Not a big deal really, but I thought I'd bring it to your attention as this is still a very new feature.
ratio = 0.9995
emsg = '%.1f%%' % (ratio * 100.0)
emsg = 'Download would not be successful, only %s available' % emsg
print emsg
emsg = '%d%%' % (ratio * 100.0)
emsg = 'Download would not be successful, only %s available' % emsg
print emsg
sander@R540:~$ python wwwww.py
Download would not be successful, only 100.0% available
Download would not be successful, only 99% available
sander@R540:~$
So using %d gives two better results:
- rounding down, no more "100.0%"
- no false idea that the measurement is exact in 1 decimal after the point