fix(observability): enrich server log on CommitMemory plugin error (#2398) #2415
Reference in New Issue
Block a user
Delete Branch "fix/2398-enrich-commitmemory-log"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Enrich the server-side log on CommitMemory plugin error with workspace, scope, namespace, error type and quoted error message. The HTTP 500 response stays the generic literal to avoid client-side leak.
Fixes #2398
SOP Checklist
Replace the bare log.Printf("Commit memory error (plugin): %v", err) with operator-diagnosis context: workspace=%s scope=%s namespace=%s err_class=%T err=%q The HTTP 500 response body stays the generic literal "failed to store memory" — zero client-side leak. Only the server-side log is enriched so recurring incidents can be distinguished in the log aggregator. Closes #239871c904309cto360d1f7cf7APPROVED on current head
360d1f7cf7. 5-axis review: scope is limited to memories.go CommitMemory error logging; the underlying err remains server-log-only and the HTTP 500 response stays the same genericfailed to store memory, so no client leak or write-path behavior change. No gate/auth/merge-control changes; BP-required contexts are present+green and mergeable=true.APPROVE on molecule-core #2415 @360d1f7c. One-file memory observability change keeps raw CommitMemory plugin error server-log-only (workspace/scope/namespace/err_class/err) while the HTTP response remains generic
failed to store memory; no client/WS/SSE leak, no behavior/gate/auth changes. BP-required contexts are present+green and mergeable=true.