sync client wants to sync .fseventsd even though it's on ignore list

JMoVS commented 3 years ago

How to use GitHub

Please use the 👍 reaction to show that you are affected by the same issue.
Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
Subscribe to receive notifications on status change and new comments.

Expected behaviour

when .fseventsd is in the ignore list, I shouldn't see notifications telling me that .fseventsd couldn't be synced

Actual behaviour

Desktop notifications being triggered that .fsevents couldn't be synced

Steps to reproduce

Have your nextcloud local sync folder on its won partition (so that .fseventsd exists on it)
Update to latest client version (3.2.1) on macOS Catalina
Have some files change so files get synced
Get message that fsevents was unsuccessfully synced

Client configuration

Client version: 3.2.1

Operating system: Mac OS Catalina 10.15.7

OS language: German

Installation path of client: default

Server configuration

Nextcloud version: 21

Storage backend (external storage): no external storage

Logs

Please use Gist (https://gist.github.com/) or a similar code paster for longer logs.

Client logfile: nextcloud desktop bug.zip
Web server error log:
Server logfile: nextcloud log (data/nextcloud.log):

github-actions[bot] commented 3 years ago

This bug report did not receive an update in the last 4 weeks. Please take a look again and update the issue with new details, otherwise the issue will be automatically closed in 2 weeks. Thank you!

JMoVS commented 3 years ago

not solved

dasaweb commented 3 years ago

Could this be related to #2728?

JMoVS commented 3 years ago

might be

dasaweb commented 3 years ago

You could test this by temporarily using client version 3.0.3. If your problem disappears, it could be the same problem as described in #2728.

JMoVS commented 3 years ago

I have since changed my setup and can no longer easily test

JMoVS commented 3 years ago

to reproduce, one could try to put the nextcloud syncing folder directly in a disk so that the disk would have a .fsevents folder and hence would allow to test if exclusion now works

mgallien commented 3 years ago

to reproduce, one could try to put the nextcloud syncing folder directly in a disk so that the disk would have a .fsevents folder and hence would allow to test if exclusion now works

I guess the plan is rather to forbid usage of a disc root folder. That is already impossible with virtual files on Windows and seems like Mac OS would benefit from that also.

JMoVS commented 3 years ago

also an option ;-)

nextcloud / desktop