v3.15.0
Changelog for reva 3.15.0 (2026-10-28)
The following sections list the changes in reva 3.15.0 relevant to reva users. The changes are ordered by importance.
Summary
- Fix #5964: Give each cephmount thread request its own response channel
- Fix #5946: Remove a data race when
revadstarts multiple configs - Chg #5842: Declare HTTP routes, and route between services with a gateway
- Enh #5951: Add help-
to the Makefile - Enh #5950: Add a help target to the Makefile
- Enh #5938: Report the progress of the expired shares job
- Enh #5937: Report the progress of the orphan reconciliation
- Enh #5936: Report the progress of the shallow reconciliation
- Enh #5947: Rewrite the reva CLI on cobra
- Enh #5948: Color the reva CLI help
- Enh #5934: Let periodic jobs report progress
- Enh #5940: Report the progress of the job retention
- Enh #5939: Report the progress of the takeout cleanup
- Enh #5935: Report the progress of takeouts
Details
Bugfix #5964: Give each cephmount thread request its own response channel
All requests of a cephmount user thread shared one response channel. When a request was cancelled, its response stayed in the channel, and the next request of that user read it and failed with “input/output error”. Every later request of that user failed the same way, until the user was idle for 5 minutes. Parallel requests of one user could also read each other’s responses. Each request now has its own response channel.
Bugfix #5946: Remove a data race when
revadstarts multiple configsWhen
revadstarted several configs, each instance registered itself in a package level slice from its own goroutine. Append is not thread-safe, so the slice could become corrupted. Nothing ever read the slice, so it was removed.Change #5842: Declare HTTP routes, and route between services with a gateway
HTTP services used to hand the server one handler mounted under a configurable prefix, and route inside it however they liked. They now declare their routes on a router built on the standard library’s ServeMux, and the server serves all of them from one table: patterns are absolute, methods are part of the route, and the paths exempt from authentication are declared on the routes themselves rather than kept in a separate list that could drift.
Each service advertises its routes in the service registry, which is what the new
gatewayHTTP service mirrors: a single entry point that forwards a request to the service owning the route it matches, configured with no paths at all. It resolves the serving node per request and forwards the path exactly as it arrived, as WebDAV clients require, leaving authentication to the service.Two consequences for existing configurations. The
prefixsetting of every HTTP service is gone, so a deployment that set one to a non-default value has to move its clients. Andocdav, previously mounted at the root and therefore answering every unmatched URL, now declares the entry points it actually serves, so anything else gets a 404.Services no longer expose a prefix at all: the routes say where they serve. The two whose URL a peer builds from the registry, the data provider and the data gateway, advertise the path they are served under themselves.
The WebDAV service used to route itself, walking the request path segment by segment through nested switches spread over several files, accumulating the base URI as it went and rewriting the URL in place. It now declares its entry points, each with the base URI it reports fixed at declaration and a handler declared per method, so the router picks the operation and refuses a method nobody serves. What is left of the walk is one segment read per subtree, for the user, space, share or token its URL carries.
Enhancement #5951: Add help-
to the Makefile make help-<target>shows the details of a target: its description, its variables and its prerequisites. The details come from the comment block above the target.Enhancement #5950: Add a help target to the Makefile
make helplists the documented targets by section, colored on a terminal. A target is listed when its line has a## description.Enhancement #5938: Report the progress of the expired shares job
The job reports the expired shares handled so far, with the removed and failed counts.
Enhancement #5937: Report the progress of the orphan reconciliation
The orphan check reports the shares and links checked so far, with the orphaned, skipped and failed counts.
Enhancement #5936: Report the progress of the shallow reconciliation
The shallow check reports its phase, the shares or spaces done so far and its running totals.
Enhancement #5947: Rewrite the reva CLI on cobra
The console mode is removed and commands are noun-verb groups with
--longflags and shell completion. Settings come from flags, env orreva config set, and errors give correct exit codes.Enhancement #5948: Color the reva CLI help
The help and the errors of the reva CLI are colored on a terminal.
NO_COLORturns the colors off, also in the admin tables and logs.Enhancement #5934: Let periodic jobs report progress
A periodic job can set
RunWithProgressto report how far it has got, like an on-demand job.Enhancement #5940: Report the progress of the job retention
The
rjobs.retentionjob reports how many runs it pruned so far.Enhancement #5939: Report the progress of the takeout cleanup
The cleanup job reports the takeout folders checked so far and how many it deleted.
Enhancement #5935: Report the progress of takeouts
The takeout job reports the bytes archived so far, so
reva admin jobsshows how far a takeout has got.