Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
Sign upqvm-copy-to-vm incorrect progress report #1519
Comments
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
Rudd-O
commented
Dec 18, 2015
|
Round up? That might be the correct answer. |
marmarek
added
bug
C: core
P: minor
labels
Jan 6, 2016
marmarek
added this to the Release 3.0 updates milestone
Jan 6, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
bnvk
Feb 18, 2016
Agree. This discrepancy has made me question if the copying was completed correctly of if some file failed to finish!
bnvk
commented
Feb 18, 2016
|
Agree. This discrepancy has made me question if the copying was completed correctly of if some file failed to finish! |
bnvk
referenced this issue
Mar 15, 2016
Open
Improving inter-VM file copy / move UX master ticket #1839
marmarek
modified the milestones:
Release 3.0 updates,
Release 3.1 updates
Nov 19, 2016
This comment has been minimized.
Show comment
Hide comment
This comment has been minimized.
unman
Apr 22, 2017
Member
@marmarek There are cases where the report is correct, so Rudd-O's proposed solution wont work.
I think the problem arises because the target figure comes from du operation on the sender, and the "progress" figure comes from the recipient, using a division in C (x/1024) to get Kb value. Division in C always truncates to zero so there will always be the possibility of discrepancy.
The only way I can think of guaranteeing there would be no discrepancy would be to write after a successfull copy , duplicating the target figure (sent TARGET of TARGET ), which is pretty monstrous.
|
@marmarek There are cases where the report is correct, so Rudd-O's proposed solution wont work. |
kirill9000 commentedDec 15, 2015
It copies file fully, but reports in a manner like:
sent 10004/10005 KBor evensent 0/1 KBfor small files and that may confuse some users.