mirror of
https://github.com/galaxyproject/galaxy.git
synced 2026-09-21 05:45:37 +08:00
mvdbeek
ec5fa78528
Comparing a stamped CVMFS revision at boot is unsound for the canonical publishing workflow: the populator runs inside the publish transaction at revision N, the publish commits as N+1, so every client reads current != stamped forever. The revision can't record the bump it is part of. It's also unnecessary. A read-only store ships in the same transaction as the tools it indexes, so a schema-valid index (load_index already gates on INDEX_SCHEMA_HASH) is authoritative by construction — trust it. index_is_fresh on a read-only store now returns whether the index loads; False means no loadable index at all, which the composite warns about and continues (only the publisher can fix it). freshness: cvmfs is thereby watcher-only: the watcher compares current revision against the last value seen on this client — transition detection, immune to the off-by-one. The writable default store keeps the tool_confs stamp-and-compare, where populate and boot share a host and the comparison is meaningful. Claude-Session: https://claude.ai/code/session_018L7ZmCv2ubKA3JNeSL8Pkr