Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] poor rename handling by clients/server, ends up overwriting files #2875

Open
working-name opened this issue Jan 18, 2025 · 1 comment

Comments

@working-name
Copy link

Describe:

It's quite frustrating working with Seadrive across multiple computers when it comes to renaming files. If I rename a file on one client, I expect the other clients to pick up on it. Sometimes it doesn't, or if it does it ends up overwriting my newer version file with that laggy client's old file.

It's a bit better in later versions of the clients, but still not quite there yet.
macOS specifically used to keep its own files as duplicates to the renamed files changed on another client, prompting manual cleanup.

Result:

I lose work or end up doing the same thing all the while wondering if I have memory problems.

Image

Expected result:

I expect all seadrive/seaclient to react to file renames and not overwrite files silently.

Info:

Server Version: 11.0.16
Seadrive 3.0.10+ (linux/mac/windows)
Seaclient 9.0.11 (linux/mac/windows)

@killing
Copy link
Member

killing commented Jan 22, 2025

Your issue may be due to server or client side issue, or combination of both. In many cases it may not be a bug. Without detailed logs from both the client and the server as well as change history of the library, it's hard to solve it, just based on your general description. You could send the information to [email protected].

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants