time stamp is wrong on 1.55a

[nix4me]

I've found that crossftp client 1.55a gets the year wrong on timestamps. It thinks the files are a year older, 2008.

Its consistant from both a remote listing and a local listing.

[alex]

Thanks for the question. Did not find this problem before. Can you try to go the the remote folder that has this problem, capture a folder's content capture, and then choose Tools -> Show Raw Directory. The folder's content will be outputed in the log message window. Can you paste it here? Or you can send the content to support_at_crossftp.com Thanks.

[nix4me]

i sent you an email with some details.

[nix4me]

Any other info I can provide to help with a fix for this?

[alex]

If you can provide a temporary test account for your problem server, it would be better. It will only be used for the tiny list test. Thanks.

[nix4me]

I provided an account via email.

Also, here is some more info. Both 1.55a and the current nightly exhibit this behaviour.
1.50a does not, it shows correct time.

[alex]

Thanks for your information. It seems that your local machine probably has a wrong date time (one year older) so that the parser is initialized with a wrong date. Please check your local machine's time.

[nix4me]

local machine time is fine. remote machine where the dirs are being made is on UTC but year is current. This doesn't explain why year is 2008. It seems to me that crossftp is having trouble distinguishing the day and year when the day is diffent (due to UTC) than the local machine. I sent screenshots and more info via email.

And, version 1.50a is fine. 1.55a has trouble, nightly has trouble.

[alex]

This problem should have been fixed.

[nix4me]

Good news, thanks. I look forward to trying out a nightly to test the fix.

[nix4me]

Any update on this fix yet?

[alex]

This is provided in the nightly build version, but not the release yet.

[nix4me]

the nightly is working correctly in regard to this time stamp issue. thanks for fixing it.

[xyruzh]

I am not quite familiar with this problem as I have not yet experienced this thing before. Maybe you could provide a screen shot showing the problem so we could sort it our properly. As I understand, you local machine should not be causing the problem as they have the right local machine. Maybe it could be because of the remote machine.