Ticket #4499 (closed defect: fixed)
reget: wrong timestamp when resuming copy operation
Reported by: | cri | Owned by: | andrew_b |
---|---|---|---|
Priority: | major | Milestone: | 4.8.31 |
Component: | mc-core | Version: | master |
Keywords: | Cc: | ||
Blocked By: | Blocking: | ||
Branch state: | merged | Votes for changeset: | committed-master |
Description
Steps to reproduce:
- Initiate a file copy operation from a remote FTP server
- Interrupt the operation (e.g. kill the mc terminal)
- Repeat step 1. and choose "Reget" to resume the copy operation
Expected result: the timestamp of the file copied on the local system should be the same of the file on the FTP server (as it always happens when the copy operation is not interrupted/resumed)
Actual result: the timestamp of the file copied on the local filesystem represents the "current" time (i.e. when the copy operation ended)
Notes:
- The bug doesn't happen when using the Suspend / Continue commands, you have to somehow kill the operation and use the Reget command
- I only tested this with FTP, maybe it happens also with other VFSs?
Change History
comment:1 in reply to: ↑ description Changed 16 months ago by andrew_b
comment:2 Changed 16 months ago by andrew_b
- Owner set to andrew_b
- Status changed from new to accepted
- Milestone changed from Future Releases to 4.8.31
- Summary changed from FTP reget: wrong timestamp when resuming copy operation to reget: wrong timestamp when resuming copy operation
comment:3 Changed 16 months ago by andrew_b
- Branch state changed from no branch to on review
Branch: 4499_reget_timestamp.
changeset:44b01d0fa04711fb942d7583f691d13d8cf1b845
comment:4 Changed 15 months ago by andrew_b
- Votes for changeset set to andrew_b
- Branch state changed from on review to approved
comment:5 Changed 15 months ago by andrew_b
- Status changed from accepted to testing
- Votes for changeset changed from andrew_b to committed-master
- Resolution set to fixed
- Branch state changed from approved to merged
Merged to master: [c1263686a73c31001ae9fa5943cc9c114fa555b3].
Note: See
TracTickets for help on using
tickets.
Replying to cri:
It happens with any VFSes including local.