nextcloud / desktop

💻 Desktop sync client for Nextcloud
https://nextcloud.com/install/#install-clients
GNU General Public License v2.0
2.97k stars 784 forks source link

[Bug]: Client not syncing when empty TAGS file is in folder #5605

Open ThatsStas opened 1 year ago

ThatsStas commented 1 year ago

⚠️ Before submitting, please verify the following: ⚠️

Bug description

I'm syncing emacs org files (plaintext) across machines. When the notes folder contains a TAGS file with no content, nextcloud refuses to sync any changes from client to the server any more. The other way round works.

I'm running the server inside a docker container. I couldn't find any useful logs on the files chaned neither server-side nor client-side.

I though I share this since this issue caused my a few hours to figure out.

Pls let me know if I can somehow assist with the investigation.

Steps to reproduce

Create some files in a empty directory. They should appear in the nextcloud WebUI.

Add a empty file called TAGS in the same directory. Changes to already existing files are not going to be synced any more. The client is convinced it's done syncing though.

Interestingly, when making a copy of the folder, only the subfolders (w/o content) are synced, no matter what's the content.

Expected behavior

All files are synced.

Which files are affected by this bug

.

Operating system

Linux

Which version of the operating system you are running.

Ubuntu 22.04.2 LTS @ 5.19.0-38-generic stock kernel

Package

Distro package manager

Nextcloud Server version

image: nextcloud:25.0

Nextcloud Desktop Client version

3.4.2

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Enabled

Are you using an external user-backend?

Nextcloud Server logs

No response

Additional info

No response

joshtrichards commented 10 months ago

This was probably fixed by #5871.

Are you still seeing this behavior today?

ThatsStas commented 7 months ago

Hi. Sorry for the late reply. I just checked and the issue unfortunately still persists.