The following sections list the changes in reva 1.9.1 relevant to reva users. The changes are ordered by importance.
This was introduced on https://github.com/cs3org/reva/commit/117adad while porting the configuration on .drone.yml to starlark.
Force golang:alpine3.13 as base image to prevent errors from Make when running on Docker <20.10 as it happens on Drone ref.https://gitlab.alpinelinux.org/alpine/aports/-/issues/12396
https://github.com/cs3org/reva/pull/1843 https://github.com/cs3org/reva/pull/1844 https://github.com/cs3org/reva/pull/1847
owncloudsql string when returning errors and removed copyMD as it does not need to copy
metadata from files.
In the owncloud storage driver when we delete a file we append the deletion time to the file name. If two fast consecutive deletes happened, the deletion time would be the same and if the two files had the same name we ended up with only one file in the trashbin.
The decomposedfs was not using the original file mtime during uploads.
When an LDAP server does not provide numeric uid or gid properties for a user we now fall back to a
nobody id (default 99).
As a workaround for listing larger folder we raised the
MaxCallRecvMsgSize to 10MB. This
should be enough for ~15k files. The proper fix is implementing ListContainerStream in the
gateway, but we needed a way to test the web ui with larger collections.
In order to upgrade mattn/go-sqlite3 to v1.14.7, the odic provider service is removed, which is possible because it is not used anymore
The PI (programmatic interface) of the GOCDB will soon require an API key; this PR adds the ability to configure this key in Mentix.
The ListStorageSpaces call now allows listing all user homes and shared resources using a
storage space id. The gateway will forward requests to a specific storage provider when a
filter by id is given. Otherwise it will query all storage providers. Results will be
deduplicated. Currently, only the decomposed fs storage driver implements the necessary
logic to demonstrate the implmentation. A new
/dav/spaces WebDAV endpoint to directly
access a storage space is introduced in a separate PR.
The readonly interceptor could be used to configure a storageprovider in readonly mode. This could be handy in some migration scenarios.
We replaced ResourceEqual with ResourceIDEqual where possible.
The recycle API could only act on the root items of the trashbin. Meaning if you delete a deep tree, you couldn’t restore just one file from that tree but you had to restore the whole tree. Now listing, restoring and purging work also for sub paths in the trashbin.