Commit e02f1de
committed
Bump setup.py __version__ to 1.12.1 so cache invalidation finally fires
setup.py has been pinned at __version__ = "1.8.0" since the 1.8 line,
so importlib.metadata.version('vfbquery') returns "1.8.0" inside every
running worker no matter which git tag (or Docker tag) ships the wheel.
solr_result_cache.py:251-258 checks
current_version = _normalize_version(_get_package_version())
cached_version = _normalize_version(cached.get("package_version")
or cached.get("version"))
if current_version and cached_version != current_version: invalidate
With both sides reduced to "1.8" (major.minor), every cached entry is
considered current and never invalidates — even after upgrading from
v1.10.1 -> v1.11.0 -> v1.12.0. That is why SimilarMorphologyTo,
PaintedDomains, NeuronsPresynapticHere, LineageClonesIn,
TractsNervesInnervatingHere etc still return v1.10.x-era shapes on the
live API despite all four workers showing image tag v1.12.0 in Rancher.
Bumping __version__ to 1.12.1 normalizes to "1.12" — old "1.8" entries
mismatch and self-invalidate on next read.
Future-proof: derive __version__ from the git tag (setuptools-scm or
similar) so this can't drift again. Deferred to a follow-up.1 parent ea5c4d6 commit e02f1de
1 file changed
Lines changed: 1 addition & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3 | 3 | | |
4 | 4 | | |
5 | 5 | | |
6 | | - | |
| 6 | + | |
7 | 7 | | |
8 | 8 | | |
9 | 9 | | |
| |||
0 commit comments