Wrong modified time in Sublime text 3

[Alecto]

On the server, the correct time.
When I copy files manually - they are with correct time.
If synchronization is performed - they have wrong time (+3).
This problem has been known for a long time, has not yet been fixed?

show info:
http://image.prntscr.com/image/6f336ec7f3454d84b1b5b8290779dc92.png

i tried "time_offset" - It does not affect the time.

[bigrepository]

For some reason, i am encountering the same issue since switching to a new server ... my modified-time is +2hours to my local time (Austria UTC+1)... time_offset doesn't seem to have any effect.

[steve123go]

Same here.. after FTPSync update.. files on my server are 4 hours behind !

time_offset of 14400 does not help.

FTPSync MFMT:
getmtime: 1477839261.0587053
encoded: 20161030105421

[bigrepository]

Adding
"set_remote_lastmodified": false,
"time_offset": -60,
seems to fix it for now (at least in my case).

[steve123go]

that doesn't make sense but.. it works !
. . many thanks ! ( this beats the hell out of constant
cache clearing due to old timestamps : )

    "time_offset": -240, // [seconds]
    // "always_sync_local_permissions": true,

    // Only if the server has MFMT extension installed
     "set_remote_lastmodified": false,

[SylwesterZarebski]

@bigrepository: setting set_remote_lastmodified to false disables MFMT completely, thus do not set time at all, just using transfer time.

The bug is probably in:

self.voidcmd("MFMT " + self.__encodeTime(os.path.getmtime(file_path)) + " " + path)

Which do not use time_offset at all.

Ok, i think proper fix would be change in ftpsyncwrapper.py line 1019 (method __encodeTime()):

        time = datetime.datetime.fromtimestamp(timestamp)

to

        time = datetime.datetime.utcfromtimestamp(timestamp)