opensource/galaxy
3
0
Fork 0
mirror of https://github.com/galaxyproject/galaxy.git synced 2026-09-21 05:45:37 +08:00
Code Issues Packages Projects Releases Wiki Activity

source store: stop calling the cvmfs revision a consistency proof

Browse Source 
The boot path trusts read-only stores by construction; the stamped
revision could never match (populated at revision N inside the publish
transaction, clients see N+1). The probe only feeds the watcher's
change detection, so say that.
This commit is contained in:
mvdbeek
2026-07-13 15:26:21 +02:00
parent 556c7c8895
commit 7876758c12
1 changed files with 8 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
lib/galaxy/tools/source_store/freshness.py
+8 -3
View File
@@ -19,9 +19,14 @@ Two probe kinds exist:
automatically.
- ``cvmfs``: the CernVM-FS repository revision, read from the
``user.revision`` extended attribute the CVMFS client exposes on the
mount point. One syscall covers every file in the repository. For a
store whose sqlite bundle is published in the same CVMFS transaction as
the tools it indexes, a matching revision is a hard consistency proof.
mount point. One syscall covers every file in the repository. This
probe only feeds the watcher's change detection: a revision transition
means a new publish landed and cached state should reload. It is *not*
a boot-time token comparison — read-only stores are trusted as
published (see ``SqlAlchemyToolSourceStore.index_is_fresh``: the bundle
ships in the same transaction as the tools it indexes), and a stamped
revision could never match anyway, since the publisher populates inside
the transaction at revision N while clients see N+1.
"""
import hashlib