Jörn Friedrich Dreyer
Jörn Friedrich Dreyer
Thesize diff calculation might be racy: - there is an existing file with size 10 - upload A is started and writes a 5 byte file - this will set...
so the error seems to be that the revision has no blobid attribute set ... ```console {"level":"error","error":"error reading blobid xattr: xattr.get /drone/src/tmp/reva/data/spaces/28/175508-ec25-103d-820e-9b9f4a005ed7/nodes/bd/1b/06/73/-b87d-49f8-bcab-535b42cc37dc.REV.2023-09-20T17:16:18.608228057Z.mlock user.ocis.blobid: no data available","revision":"/drone/src/tmp/reva/data/spaces/28/175508-ec25-103d-820e-9b9f4a005ed7/nodes/bd/1b/06/73/-b87d-49f8-bcab-535b42cc37dc.REV.2023-09-20T17:16:18.608228057Z.mlock","time":"2023-09-20T17:16:26.941046467Z","message":"error reading blobid attribute"} [90m2023-09-20...
- [ ] we should move the code to get the list of uploads from decompesedfs to a tus package ... uploads are not storagedriver specific, but tus datastore specific....
I rebased on top of latest reva. no big difference, looking at the current errors. I don't know what is going on with the S3NG driver. IT does not seem...
da39a3ee5e6b4b0d3255bfef95601890afd80709 is the hash for the empty string ... maybe reading back the upload from ceph does not work?
Indeed. The added log line appears: `internal error: mismatching upload length. expected 4, could only copy 0` 👀 ``` 2023-11-01 15:13:14.018 DBG ../../../pkg/rhttp/rhttp.go:248 > http routing: head=data tail=/simple/ef186ae941dd9250bf46163afe2772b6+2~PxXm3ze5qcW3AfYzPWkgfjAmKQmrtNG svc=data pid=11...
the cs3 validation trests do not send the size: ``` 2023-11-02 11:46:45.461 DBG ../../../pkg/storage/utils/decomposedfs/upload.go:235 > Decomposedfs: initiated upload headers={"providerID":"1284d238-aa92-42ce-bdc4-0b0000009157"} info={"ID":"06a666a5d9531506c1ed5ab1d96cba02+2~xksXoAaOlflsXkAhUDEM5NsVKJ2iD73","IsFinal":false,"IsPartial":false,"MetaData":{"cs3.ExecutantId":"ddc2004c-0977-11eb-9d3f-a793888cd0f8","cs3.ExecutantIdp":"http://localhost:20080","cs3.ExecutantType":"primary","cs3.ExecutantUserName":"admin","cs3.LogLevel":"debug","cs3.NodeId":"","cs3.NodeParentId":"5dd5fd83-7baf-4f62-9812-a213249d994a","cs3.RevisionTime":"2023-11-02T11:46:45.451162592Z","cs3.SpaceOwnerOrManager":"ddc2004c-0977-11eb-9d3f-a793888cd0f8","cs3.SpaceRoot":"ddc2004c-0977-11eb-9d3f-a793888cd0f8","cs3.dir":"/a-folder/a-sub-folder","cs3.filename":"testfile.txt","cs3.lockid":"","cs3.providerID":"1284d238-aa92-42ce-bdc4-0b0000009157"},"Offset":0,"PartialUploads":null,"Size":0,"SizeIsDeferred":true,"Storage":{"Bucket":"test","Key":"06a666a5d9531506c1ed5ab1d96cba02","Type":"s3store"}} nodeid= pid=11 pkg=rgrpc spaceid=ddc2004c-0977-11eb-9d3f-a793888cd0f8 traceid=bd2759a62c350e8ff677f1266e7c6235 uploadLength=0 2023-11-02 11:46:45.461 INF ../../../internal/grpc/services/storageprovider/storageprovider.go:455...
@micbar again ... messing with versions. The tests are writing revisions with specific mtimes, multiple times: ``` Scenario: upload the same file twice with the same mtime and a version...
I am going in circles. The old code would write a file into the `/uploads` folder of a space. Only when the upload was complete it would create a revision...
hm lots of failures when testing against ocis: https://drone.owncloud.com/owncloud/ocis/29114/28/6