fix(activitylog): log missing parent id cache entry at debug level

[junkerderprovinz]

Description

Issue #1043 reports three ERROR log lines that appear during perfectly normal file moves and deletes. @butonic already diagnosed all three as expected conditions that are simply logged at the wrong level.

Only one of the three sites lives in this repository:

Log message	Location	Fixable here?
could not delete parent id cache	services/activitylog/pkg/service/service.go	yes, fixed in this PR
failed to handle moved away item	reva/pkg/storage/fs/posix/tree/assimilation.go	no, vendored opencloud-eu/reva
could not remove lock file	reva/pkg/storage/fs/posix/tree/tree.go	no, vendored opencloud-eu/reva

This PR therefore changes the activitylog site only. The other two need a companion PR in opencloud-eu/reva followed by a dependency bump here. I am happy to open that reva PR as a follow-up if you would like.

ActivitylogService.removeCachedParentID calls ttlcache.Cache.Remove, which returns ErrNotFound ("key not found") when the key is not present. The parent id cache is filled lazily in addActivity and its entries expire, so on an ItemMoved event the key is very often simply not there. That is the normal case, not a failure, so it is now logged at debug level.

A short comment was added at the call site so the reason for the debug level is not lost.

Related Issue

• Fixes Unknown cache errors #1043 (partially, see the table above)

Small note on process: @robin-thoene mentioned in the issue that they wanted to pick this up and asked exactly the right two clarifying questions, which turned out to be correct on both counts. As the questions had not been answered and there was no visible activity since, I went ahead and prepared this change. Happy to hand it over or close this if they would still prefer to do it.

Motivation and Context

Users running an otherwise healthy instance see ERROR entries in their logs for successful operations, which is alarming and hard to distinguish from real problems. The reporter in #1043 specifically opened the issue because they thought something was broken.

How Has This Been Tested?

• test environment: go1.26.4, CGO_ENABLED=0, package services/activitylog/pkg/service
• test case 1: go test -count=1 ./services/activitylog/pkg/service/ passes
• test case 2: three new Ginkgo specs added under Describe("removeCachedParentID"):
  • at the default error level, a missing cache entry produces no log output at all (this is the actual regression from the issue)
  • at debug level, the message is emitted with "level":"debug"
  • when the entry does exist, nothing is logged and the entry is removed
• test case 3: verified the new specs genuinely guard the fix by temporarily reverting .Debug() back to .Error(), which fails 2 of the 3 specs as expected
• test case 4: go vet ./services/activitylog/... and go build ./services/activitylog/... are clean (GOOS=linux)
• test case 5: gofmt clean on both changed files

Screenshots (if appropriate):

n/a

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation added

---

AI assistance: Claude Code helped with investigation and implementation of this fix. I reviewed, tested, and take full responsibility for the change.

Assisted-by: Claude Code:claude-opus-5

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 duplication

Metric	Results
Duplication	0

View in Codacy

🟢 Coverage 100.00% diff coverage

Metric	Results
Coverage variation	Report missing for 6077e741
Diff coverage	✅ 100.00% diff coverage

View coverage diff in Codacy

Coverage variation details

	Coverable lines	Covered lines	Coverage
Common ancestor commit (6077e74)	Report Missing	Report Missing	Report Missing
Head commit (56fbed9)	84102	19355	23.01%

Coverage variation is the difference between the coverage for the head and common ancestor commits of the pull request branch: <coverage of head commit> - <coverage of common ancestor commit>

Diff coverage details

	Coverable lines	Covered lines	Diff coverage
Pull request (#3325)	1	1	100.00%

Diff coverage is the percentage of lines that are covered by tests out of the coverable lines that the pull request added or modified: <covered lines added or modified>/<coverable lines added or modified> * 100%

¹ Codacy didn't receive coverage data for the commit, or there was an error processing the received data. Check your integration for errors and validate that your coverage setup is correct.

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[rhafer]

Looks fine codewise. Just remove the the changelog item please, before we can merge.

Also you might want to read up on https://github.com/opencloud-eu/.github/blob/main/profile/AI_GUIDELINE.md

[rhafer]

Please remove this, we've switched away from calens for changelog generation last year already. The changelog directory is just a leftover (will be removed by #3339)

[junkerderprovinz]

Done, the changelog fragment is removed and pushed. Thanks for the pointer to the AI guideline too, I hadn't seen it before, I've added an Assisted-by line to the PR description to match it.