Folder size propagation not triggered by Webdav upload

[PVince81]

Steps to reproduce

1. Create a folder "test"
2. Using a Webdav client (I used cadaver), upload a file "pic.jpg" into "test"
3. In the web UI, check the size of the folder "test"

Expected result

Folder size is updated to reflect the size of the picture inside.

Actual result

Folder size is still zero.

I noticed that in the database the propagation isn't happening after upload.
However the folder size will update itself later through other mechanisms, possibly through PROPFINDs or the scanner that the web UI triggers (ajax/scan.php) or the background cron scan.

This also means that the quota value (the total used space) will not be updated directly.

Uploading through the web UI properly propagates the sizes, so it's specific to Webdav.

Versions

stable8.1 (a9524e2)

I will bisect to find out when this regression was introduced.
Not sure how critical. Setting to 8.1.1 now but 8.1.2 might be fine.

@DeepDiver1975 @icewind1991 @schiesbn

[PVince81]

Regression from v8.0.5 where it worked properly.

I suspect it might be related to the recent improvements on etag propagation.
The bisect will tell.

[PVince81]

I knew it... it's the "work directly on storage when doing webdav PUT": #12006

[PVince81]

Note: this will only affect files uploaded without chunking, since the chunking code doesn't work directly on storages (but it will eventually as per #17104)

[PVince81]

@icewind1991 can you fix this ? Thanks.

[PVince81]

Alternative for the future: update folder size in a background job: #18028