consistently omit clusters when calculating RepoSizes
authorJoey Hess <joeyh@joeyh.name>
Sat, 17 Aug 2024 15:16:21 +0000 (11:16 -0400)
committerJoey Hess <joeyh@joeyh.name>
Sat, 17 Aug 2024 15:24:14 +0000 (11:24 -0400)
commit8239824d922d6b09ce08ad16fa9b4cac05d9de23
treec7f7bbcf71e7eecd8b1023b97bd7be03a19fb736
parent61d95627f3172f892ded616d94ae37f57783d494
consistently omit clusters when calculating RepoSizes

updateRepoSize is only called on the UUID of a repository, not any
cluster it might be a node of. But overLocationLogs and overLocationLogsJournal
were inclusing cluster UUIDs. So it was inconsistent.

Currently I don't see any reason to calculate RepoSize for a cluster.
It's not even clear what it should mean, the total size of all nodes, or
the amount of information stored in the cluster in total?
Annex/RepoSize.hs
CmdLine/Seek.hs
Command/Info.hs
Logs/Location.hs