New issue
Advanced search Search tips

Issue 668068 link

Starred by 0 users
Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

MoveTreeWorkItem's rollback doesn't properly restore the prior contents of the target directory

Project Member Reported by grt@chromium.org, Nov 23 2016 
MTWI is supposed to gracefully move the target dir out of the way if it exists and then put it back during rollback. It doesn't. If we have, say A\B\C as the target dir, C is correctly moved into a temp dir initially, but then ends up being moved to A\B\C\C during rollback. I discovered this while researching issue 599084. It isn't the cause of issue 599084, but it is being tickled by it.

Comment 1 by grt@chromium.org, Nov 23 2016 

Actually, this isn't quite true. I'm still researching, but I think it only happens when the move is emulated by copy-n-delete.

Comment 2 by benhenry@google.com, Jan 11 

You started fixing this bug over two years ago. Are you still working on it? You can update the status to "archived", "wontfix", or "closed". You can remove yourself as owner and change status to "untriaged", but if this is still a real bug, please do not sit on it.

Comment 3 by grt@chromium.org, Jan 14

Labels: -OS-Windows -Pri-2 OS-iOS Pri-3
Owner: ----
Status: Available (was: Started)
I think we may still have a bug deep in there, either in the work item or in base::Move (related to issue 674135). I'm not actively working on this, however.

Comment 4 by grt@chromium.org, Jan 14

Labels: -OS-iOS OS-Windows
►

Sign in to add a comment