Zed thinks file was deleted when synced with nextcloud

[clawoflight]

Check for existing issues

• Completed

Describe the bug / provide steps to reproduce it

• edit a file stored in nextcloud
• save
• after a few seconds, zed thinks the file was deleted

Zed Version and System Specs

Zed: v0.169.2 (Zed)
OS: Linux Wayland arch unknown
Memory: 11.6 GiB
Architecture: x86_64
GPU: Intel(R) HD Graphics 5500 (BDW GT2) || Intel open-source Mesa driver || Mesa 24.3.3-arch1.2

If applicable, add screenshots or screencasts of the incorrect state / behavior

No response

If applicable, attach your Zed.log file to this issue.

No response

[notpeter]

How are you configuring your NextCloud setup?
Is it using WebDAV? FUSE? Or some other method to present a virtual filesystem?

[clawoflight]

nothing crazy or virtual. It's a normal directory, kept in sync by the official Nextcloud client.

[clawoflight]

I think I have an idea - if this is correct, you should be able to reproduce and fix very easily:
Could it be that zed sees external atomic writes as deletions?

By atomic write, I mean "write to a new temp file, replace original file once written". This is a common best practice, I would not be surprised if NextCloud does that. That would mean a new inode for the file, which zed could see as deletion.

---

That was what I thought, but once I tried to test this, I realized that I cannot reproduce the problem anymore, even with NextCloud. Did you change the deletion detection behavior recently?