mirror of
https://github.com/owncloud/ocis.git
synced 2026-10-23 23:29:02 +03:00
12d4423284
* fix: [ocisdev-1433] fix public share, add The grpc clients keepalive and more (#13020) * fix: the public share configuration and fixed graceful shutdown * fix: [OCISDEV-1433] remove GRPC_MAX_CONNECTION_AGE The setting closed healthy grpc connections on a timer so that clients would redo their DNS lookup. It never helped against the failure it was reached for - a connection whose peer stopped answering - because the age limit is enforced by the server, the grace period was left at infinity so a request already in flight was never ended, and any value without a unit suffix silently disabled it again. Detecting a peer that stops answering is now the job of the grpc clients, which ping the peer while a request is in flight. The servers here got the matching enforcement policy so they accept those pings; the client side arrives with the next reva bump. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix: Added the new variable OCDAV_DISABLE_PROPFIND_PUBLIC_LINK_RESOLUTION that disable the resolution of public link shares when answering PROPFIND requests. * chore: bump reva * fix: The keepalive added to grpc clinet * chore: bump reva * build(deps): bump go 1.26.8, grpc-go dependency --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com> * chore: bump pnpm dependencies * fix: avoid go vet false positive in userlog conversion.go The go.mod bump to go 1.26.8 made go vet flag loadTemplates' calls to t.Get(nt.Subject/nt.Message) as non-constant format strings, breaking the build for services/userlog/pkg/service. These are translation lookup keys, not printf format strings, so route the call through a local func value to defeat vet's static trace. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Documentation
To contribute to documentation please see also: Documentation
Note that when running a helper like make -C docs docs-generate locally, you will see the generated output in e.g. docs/services/. When merging a PR, the pipeline will generate the output in the master branch but finally moves it into the docs branch. You will therefore not see changes in the docs folder of the master branch!