Releases: cs3org/reva
v2.27.0
Changelog for reva 2.27.0 (2024-12-12)
The following sections list the changes in reva 2.27.0 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4985: Drop unneeded session locks
- Fix #5000: Fix ceph build
- Fix #4989: Deleting OCM share also updates storageprovider
- Enh #4998: Emit event when an ocm share is received
- Enh #4996: Get rid of some cases of unstructured logging
Details
- Bugfix #4985: Drop unneeded session locks
We no longer lock session metadada files, as they are already written atomically.
- Bugfix #5000: Fix ceph build
- Bugfix #4989: Deleting OCM share also updates storageprovider
When remvoving an OCM share we're now also removing the related grant from the storage
provider.
- Enhancement #4998: Emit event when an ocm share is received
- Enhancement #4996: Get rid of some cases of unstructured logging
v2.26.8
Changelog for reva 2.26.8 (2024-12-04)
The following sections list the changes in reva 2.26.8 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4983: Delete stale shares in the jsoncs3 share manager
- Fix #4963: Fix name and displayName in an ocm
- Fix #4968: Jsoncs3 cache fixes
- Fix #4928: Propagate lock in PROPPATCH
- Fix #4971: Use manager to list shares
- Enh #4978: We added more trace spans in decomposedfs
- Enh #4921: Polish propagation related code
Details
- Bugfix #4983: Delete stale shares in the jsoncs3 share manager
The jsoncs3 share manager now properly deletes all references to removed shares and shares
that belong to a space that was deleted
- Bugfix #4963: Fix name and displayName in an ocm
Fixed name and displayName in an ocm PROPFIND response
- Bugfix #4968: Jsoncs3 cache fixes
The jsoncs3 share manager now retries persisting if the file already existed and picks up the
etag of the upload response in all cases.
- Bugfix #4928: Propagate lock in PROPPATCH
Clients using locking (ie. Windows) could not create/copy files over webdav as file seemed to
be locked.
- Bugfix #4971: Use manager to list shares
When updating a received share the usershareprovider now uses the share manager directly to
list received shares instead of going through the gateway again.
- Enhancement #4978: We added more trace spans in decomposedfs
- Enhancement #4921: Polish propagation related code
We polished some corner cases for propagation that reduce log messages in normal operation.
v2.26.7
Changelog for reva 2.26.7 (2024-11-20)
The following sections list the changes in reva 2.26.7 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4964: Fix a wrong error code when approvider creates a new file
Details
- Bugfix #4964: Fix a wrong error code when approvider creates a new file
We fixed a problem where the approvider would return a 500 error instead of 403 when trying to
create a new file in a read-only share.
v2.26.6
Changelog for reva 2.26.6 (2024-11-19)
The following sections list the changes in reva 2.26.6 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4955: Allow small clock skew in reva token validation
- Fix #4929: Fix flaky posixfs integration tests
- Fix #4953: Avoid gateway panics
- Fix #4959: Fix missing file touched event
- Fix #4933: Fix federated sharing when using an external identity provider
- Fix #4935: Enable datatx log
- Fix #4936: Do not delete mlock files
- Fix #4954: Prevent a panic when logging an error
- Fix #4956: Improve posixfs error handling and logging
- Fix #4951: Pass the initialized logger down the stack
Details
- Bugfix #4955: Allow small clock skew in reva token validation
Allow for a small clock skew (3 seconds by default) when validating reva tokens as the different
services might be running on different machines.
- Bugfix #4929: Fix flaky posixfs integration tests
We fixed a problem with the posixfs integration tests where the in-memory id cache sometimes
hadn't caught up with the cleanup between test runs leading to flaky failures.
- Bugfix #4953: Avoid gateway panics
The gateway would panic if there is a missing user in the context. Now it errors instead.
- Bugfix #4959: Fix missing file touched event
We have fixed an issue where the file touched event was not being triggered when an office
document was created.
- Bugfix #4933: Fix federated sharing when using an external identity provider
We fixes and issue that caused federated sharing to fail when the identity provider url did not
match the federation provider url.
- Bugfix #4935: Enable datatx log
We now pass a properly initialized logger to the datatx implementations, allowing the tus
handler to log with the same level as the rest of reva.
- Bugfix #4936: Do not delete mlock files
To prevent stale NFS file handles we no longer delete empty mlock files after updating the
metadata.
- Bugfix #4954: Prevent a panic when logging an error
We fixed a panic when constructing a path failed to get the parent for a node.
- Bugfix #4956: Improve posixfs error handling and logging
We improved error handling and logging in the posixfs storage driver.
- Bugfix #4951: Pass the initialized logger down the stack
We now make the initialized logger available to grpc services and storage drivers, which
allows for easier and more uniform logging.
v2.26.5
Changelog for reva 2.26.5 (2024-11-12)
The following sections list the changes in reva 2.26.5 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4926: Make etag always match content on downloads
- Fix #4920: Return correct status codes for simple uploads
- Fix #4924: Fix sync propagation
- Fix #4916: Improve posixfs stability and performance
Details
- Bugfix #4926: Make etag always match content on downloads
We added an openReaderfunc to the Download interface to give drivers a way to guarantee that the
reader matches the etag returned in a previous GetMD call.
- Bugfix #4920: Return correct status codes for simple uploads
Decomposedfs now returns the correct precondition failed status code when the etag does not
match. This allows the jsoncs3 share managers optimistic locking to handle concurrent writes
correctly
- Bugfix #4924: Fix sync propagation
Fixes the defers in the sync propagation.
- Bugfix #4916: Improve posixfs stability and performance
The posixfs storage driver saw a number of bugfixes and optimizations.
v2.26.4
Changelog for reva 2.26.4 (2024-11-07)
The following sections list the changes in reva 2.26.4 relevant to
reva users. The changes are ordered by importance.
Summary
Details
- Bugfix #4917: Fix 0-byte file uploads
We fixed an issue where 0-byte files upload did not return the Location header.
- Bugfix #4918: Fix app templates
We fixed the app templates by using the product name of the providerinfo instead of the provider
name.
v2.26.3
Changelog for reva 2.26.3 (2024-11-06)
The following sections list the changes in reva 2.26.3 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4908: Add checksum to OCM storageprovider responses
- Enh #4910: Bump cs3api
- Enh #4909: Bump cs3api
- Enh #4906: Bump cs3api
Details
- Bugfix #4908: Add checksum to OCM storageprovider responses
When the remote instance of the OCM storage provider returns file checksums in its PROPFIND
responses we're now passing them through to in Stat responses. This allows e.g. the oCIS
thumbnailer to work with ocm shares.
- Enhancement #4910: Bump cs3api
- Enhancement #4909: Bump cs3api
- Enhancement #4906: Bump cs3api
v2.26.2
Changelog for reva 2.26.2 (2024-10-28)
The following sections list the changes in reva 2.26.2 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4902: Fix quota calculation
Details
- Bugfix #4902: Fix quota calculation
Quota would show "exceeded" when remaining quota was 0 because total was 0.
v2.26.1
Changelog for reva 2.26.1 (2024-10-25)
The following sections list the changes in reva 2.26.1 relevant to
reva users. The changes are ordered by importance.
Summary
- Enh #4897: Fix remaining quota calculation
Details
- Enhancement #4897: Fix remaining quota calculation
Remaining quota should only be total - used and not take disk space into account.
v2.26.0
Changelog for reva 2.26.0 (2024-10-21)
The following sections list the changes in reva 2.26.0 relevant to
reva users. The changes are ordered by importance.
Summary
- Fix #4880: Kept historical resource naming in activity
- Fix #4874: Fix rename activity
- Fix #4881: Log levels
- Fix #4884: Fix OCM upload crush
- Fix #4872: Return 409 conflict when a file was already created
- Fix #4887: Fix ShareCache concurrency panic
- Fix #4876: Fix share jail mountpoint parent id
- Fix #4879: Fix trash-bin propfind panic
- Fix #4888: Fix upload session bugs
- Fix #4560: Always select next before making CS3 calls for propfinds
- Enh #4893: Bump dependencies and go to 1.22.8
- Enh #4890: Bump golangci-lint to 1.61.0
- Enh #4886: Add new Mimetype ggp
- Enh #4809: Implement OCM well-known endpoint
- Enh #4889: Improve posixfs stability and performance
- Enh #4882: Indicate template conversion capabilties on apps
Details
- Bugfix #4880: Kept historical resource naming in activity
Kept historical resource naming after renaming in activity for shares and public links.
- Bugfix #4874: Fix rename activity
We fixed the activity when file with file-id gives move activity instead of rename.
- Bugfix #4881: Log levels
We changed the following log levels:
ERRORtoDEBUGininternal/grpc/services/usershareproviderwhen getting received
shares
- Bugfix #4884: Fix OCM upload crush
We fixed an issue where a federated instance crashed when uploading a file to a remote folder.
Fixed the cleanup blob and meta of the uploaded files.
- Bugfix #4872: Return 409 conflict when a file was already created
We now return the correct 409 conflict status code when a file was already created by another
upload.
- Bugfix #4887: Fix ShareCache concurrency panic
We fixed an issue where concurrently read and write operations led to a panic in the ShareCache.
- Bugfix #4876: Fix share jail mountpoint parent id
Stating a share jail mountpoint now returns the share jail root as the parent id.
- Bugfix #4879: Fix trash-bin propfind panic
We fixed an issue where a trash-bin propfind request panicked due to a failed and therefore
nil resource reference lookup.
- Bugfix #4888: Fix upload session bugs
We fixed an issue that caused a panic when we could not open a file to calculate checksums.
Furthermore, we now delete the upload session .lock file on cleanup.
- Bugfix #4560: Always select next before making CS3 calls for propfinds
We now select the next client more often to spread out load
- Enhancement #4893: Bump dependencies and go to 1.22.8
- Enhancement #4890: Bump golangci-lint to 1.61.0
- Enhancement #4886: Add new Mimetype ggp
Adds a new mimetype application/vnd.geogebra.pinboard (ggp) to the app-registry
- Enhancement #4809: Implement OCM well-known endpoint
The wellknown service now implements the /.well-known/ocm endpoint for OCM discovery.
The unused endpoints for openid connect and webfinger have been removed. This aligns the
wellknown implementation with the master branch.
- Enhancement #4889: Improve posixfs stability and performance
The posixfs storage driver saw a number of bugfixes and optimizations.
- Enhancement #4882: Indicate template conversion capabilties on apps
We added information to the available app providers to indicate which mimetypes can be used for
template conversion.