I have a couple of local directories I keep in sync with files from a FTPS server. On a daily basis, I do a folder compare, and pull down files from the server, and use the server timestamp for the files copied to my local directory.
Yesterday, these 2 directories were in sync, with no differences. Today after upgrading to BC 3.1.0, all of the files show up as different.
I took a screenshot with 3.1.0, and then downgraded to 3.0.15 to see the differences. All of the files on the server seem to have a different time -- they are all off by minute.
For example, in 3.0.15 a file had a timestamp of 3:11 PM (on the server, and also on my local machine), but now in 3.1.0 this same file has a timestamp of 3:10 PM on the server, so it shows up as different.
Is this a bug that was fixed between 3.0.15 and 3.1.0 where the previous version may have been pulling incorrect timestamps? Or, is this a new bug in 3.1.0?
Note: for this FTP profile, I'm manually telling BC the timezone (GMT-5).
Yesterday, these 2 directories were in sync, with no differences. Today after upgrading to BC 3.1.0, all of the files show up as different.
I took a screenshot with 3.1.0, and then downgraded to 3.0.15 to see the differences. All of the files on the server seem to have a different time -- they are all off by minute.
For example, in 3.0.15 a file had a timestamp of 3:11 PM (on the server, and also on my local machine), but now in 3.1.0 this same file has a timestamp of 3:10 PM on the server, so it shows up as different.
Is this a bug that was fixed between 3.0.15 and 3.1.0 where the previous version may have been pulling incorrect timestamps? Or, is this a new bug in 3.1.0?
Note: for this FTP profile, I'm manually telling BC the timezone (GMT-5).
Comment