Opened 6 weeks ago

Last modified 8 days ago

#13120 new Bug report

"Synchronization cannot handle duplicated file or directory names."

Reported by: Philip De Lancie Owned by:
Priority: normal Component: FileZilla Client
Keywords: sync duplicate name Cc:
Component version: 3.67.1 Operating system type: OS X
Operating system version: both 12.7.5 and 14.5

Description

I have been using FileZilla Pro (currently on 2022 Mac Studio M1 Max on Monterey 12.7.5, and MBP Sonoma 14.5) for years to sync from a local source to a remote server. The directory structure has been more or less constant. I recently upgraded to 3.67.0 and started getting this error in a popup during sync: "Synchronization cannot handle duplicated file or directory names." There is no duplicate folder or file within any given folder in the source directory; this would be impossible as the OS (Mac Monterey 12.7.5) would not allow you to create a file with the same name in any given folder. Nor are there, so far as I can tell, any duplicate hidden files. There are 20+ folders and thousands of files in the project I'm trying to sync, but I've narrowed it down to two folders that, when removed, the problem is no longer there -- Sync continues as normal without the error popup. There are no duplicate files that I can find within either of the folders, so I assume that the problem is with the folder names. These folders do have the same name, but they're not in the same directory, thus the path is different, and as I said these names have been constant for years without creating any sync problem.

At this point I can only update my site manually (not ideal; syncing is why I went Pro). I upgraded to 3.67.1 today and am still experiencing the error.

Attachments (2)

Screen Shot 2024-07-09 at 4.16.30 PM.png (148.6 KB ) - added by Philip De Lancie 6 weeks ago.
Screenshot with error popup
Screen Shot 2024-07-29 at 10.05.10 AM.png (248.1 KB ) - added by Philip De Lancie 6 weeks ago.
Shows directory structure in which FZ is finding the names of two directories to be "duplicate" while a 3rd directory of the same name at equivalent path is not considered a duplicate.

Download all attachments as: .zip

Change History (6)

by Philip De Lancie, 6 weeks ago

Screenshot with error popup

comment:1 by Tim Kosse, 6 weeks ago

Priority: blockernormal
Status: newmoreinfo

Are there any files with non-ASCII characters? Depending on encoding and normalization forms, two filenames with different byte sequence may test as equal.

comment:2 by Philip De Lancie, 6 weeks ago

Status: moreinfonew

Hi Tim. thanks for the response.

NOTES:

  • The syncing problem is new even though the content of the source v3/z_Figures folder hasn't been changed since 2020.
  • There's also a z_Figures folder in v0, but that causes no problem.

My understanding of your non-ASCII question is that it was about the names of those directories. Does the above answer your question?

comment:3 by Philip De Lancie, 6 weeks ago

I've added a screenshot to clarify my earlier statement about "v0"

Last edited 6 weeks ago by Philip De Lancie (previous) (diff)

by Philip De Lancie, 6 weeks ago

Shows directory structure in which FZ is finding the names of two directories to be "duplicate" while a 3rd directory of the same name at equivalent path is not considered a duplicate.

comment:4 by Philip De Lancie, 8 days ago

Hi. this issue is ongoing, and continues to be a significant problem for me. It's been over 5 weeks now, so I'm wondering what the expected time frame is for addressing this. Thank you.

Note: See TracTickets for help on using tickets.