I havent’t checked/tested (yet), but I guess rclone shows 0 Bytes/s as a replacement for indefinite, when the time is (almost) 0 seconds. It is just a simple hack we programmers often use to avoid fatal errors from division by zero.
It could be that the times ticks are longer on linux, or just pure coincidence.
very nice, z80, msbasic, light pen but could it zork?
tho i am not familiar with go syntax, rclone source code style and this is just a code snippet.
i am not seeing that
"It is just a simple hack we programmers often use to avoid fatal errors from division by zero."
line 319 is avg := 0.0
as i see it, with avg, no chance of a /0
avg is never used a divisor in a divide operation
the only other time avg is used is in an addition operation a.speed = (avg +
in fact, the only chance of /0, that i see is line 326. period could be zero and there is no check on that.
that is not the case with line 320, where there is an explicit check to prevent a /0 if elapsed > 0
and even if i misinterpreted the source code and in fact, there is that /0 hack,
none of that explains the difference in reported speed in the test results from up above.
imho, this could be an issue with the display output, as there is another difference.
and as this is server side, no data is transfered, so the speed should be zero.
on windows ETA 0s
on linux ETA -
i had planed to do some more testing, but i was a bad boy this morning.
so right now, i am in a time out, forced to watch the first episode of crapple's foundation series.
oh the horror of it all. if this is the end of me and i never post again in the forum, let this be a warning to all my beloved fellow rcloners.