Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Not yet, sorry.
jay1337

Any update ?
martin

jay1337 wrote:

So you can reproduce the bug ? You've found how to fix it ?

Yes, I can reproduce it. But a fix would be difficult. So it will take time.
jay1337

martin wrote:

jay1337 wrote:

The original file was created at 0h44 UTC so 2h44 summer time so before the DST "reset" to 2h

Are you sure?
It actually works correctly for me for files created on 0:44 UTC.
I have problems with files created on 1:44 UTC. First, WinSCP logs them as 0:44 UTC. And after upload the file has 2:44 UTC. So exactly the same what you get.


You are right ! It was created at 1h44 UTC. I thought it was 0h44 because Windows displays 2h44 local time and WinSCP 0h44 UTC but WinSCP is wrong. This file comes from here : https://github.com/jsdom/whatwg-encoding/commit/04a110a0b202ecf435aacf8617fd4a568e85964e#diff-b9cfc7f2cdf78a7f4b91a753d10865a2 (hover over the date and you'll get the full timestamp).

So you can reproduce the bug ? You've found how to fix it ?
martin

jay1337 wrote:

The original file was created at 0h44 UTC so 2h44 summer time so before the DST "reset" to 2h

Are you sure?
It actually works correctly for me for files created on 0:44 UTC.
I have problems with files created on 1:44 UTC. First, WinSCP logs them as 0:44 UTC. And after upload the file has 2:44 UTC. So exactly the same what you get.
jay1337

The original file was created at 0h44 UTC so 2h44 summer time so before the DST "reset" to 2h

An anonymized log of a session beginning is attached to this post.

Thanks for working on this issue.
martin

"full session log" log file please. Including a complete header.

Also was the file created between 2-3 before or after the DST?
jay1337

As you can see in the logs:
- time of the original file is 0h44 UTC => ok with what is displayed by WinSCP in local files and Windows Explorer
- time preserved by WinSCP is 2h44 UTC => nok with original file time nor with what is diplaid by Finder (0h44 UTC) BUT ok with what is displayed by WinSCP in remote files
- time downloaded by WinSCP is 2h44 UTC

Strange...
martin

Re: Wrong Last Modified Date displayed in WinSCP for remote SFTP files modified during DST shift

Please attach a full session log file showing the problem (using the latest version of WinSCP).

To generate the session log file, enable logging, log in to your server and do the operation and only the operation that causes the error. Submit the log with your post as an attachment. Note that passwords and passphrases not stored in the log. You may want to remove other data you consider sensitive though, such as host names, IP addresses, account names or file names (unless they are relevant to the problem). If you do not want to post the log publicly, you can mark the attachment as private.
jay1337

Wrong Last Modified Date displayed in WinSCP for remote SFTP files modified during DST shift

I have an issue with daylight saving time (DST, summer time).
I use WinSCP to copy a folder on a macOS Sierra, using french local time on both. Due to DST, at 29/10/17 03:00:00, local time was reset to 29/10/17 02:00:00.
I have some files on my Windows computer with a Last Modified Date between 29/10/17 02:00:00 and 29/10/17 03:00:00 (local time).
When I copy these files from my Windows computer to my Mac computer through SFTP (default mac remote access), the Last Modified Date of copied files on my Mac are ok (checking with Finder) but they are wrong in WinSCP (it displays dates between 29/10/17 03:00:00 and 29/10/17 04:00:00).

I'm using 5.11.2 (7781) on Windows 10 64bits.

Thanks in advance for your help.