Windows vfs incorrectly thinks an implicitly hydrated 0 byte file stays dehydrated #7339
Labels
feature:vfs
native virtual files and placeholder implementation
p1-urgent
Consider a hotfix release with only that fix (ex: lose trust, money, security issue, ...)
p4-low
Low priority
type:bug
Milestone
Found while testing #7111
Right click the folder and check the availability status in the ownCloud submenu. It'll say the contents are online only.
The problem here is that since no download needs to happen the cfapi "fetch" callback doesn't trigger and the client therefore doesn't realize that the file was hydrated and can't update the database.
The text was updated successfully, but these errors were encountered: