Chris LuandGitHub 3514925581 filer: let a nested path rule turn worm off (#10503) ...

* filer: let a nested path rule turn worm off

mergePathConf ORs the booleans, so worm set on a bucket could never be
lifted on a directory under it, while every string field is overridden by
the more specific rule. Make worm tri-state instead: unset inherits, set
wins. readOnly, fsync and disableChunkDeletion keep the OR, so a nested
rule still cannot escape a lock the bucket set.

Configurations written before this carry an explicit "worm": false on
every rule, because they are marshalled with EmitUnpopulated. Reading
those back as an override would quietly drop worm from nested paths, so
filer.conf is now stamped with a version and the flag is dropped to unset
when the version predates it.

* filer: copy the worm value out of the matched rule

mergePathConf aliased the pointer into the merged result, so a caller that
wrote through it would reach into the stored rule.

2026-07-31 00:34:22 -07:00

..

java

filer: let a nested path rule turn worm off (#10503)

2026-07-31 00:34:22 -07:00

metrics

feat(metrics): Add EC rebuild/reconstruct Prometheus metrics (#10124)

2026-06-27 22:01:36 -07:00

mq_client_example

chore: execute goimports to format the code (#7983)

2026-01-07 13:06:08 -08:00