Skip to content

Commit 49ab55d

Browse files
committed
CACHING.md: don't claim a release number for the fix
1 parent 553c7a1 commit 49ab55d

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

‎CACHING.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -462,7 +462,7 @@ instances = vfb.get_instances('FBbt_00003748') # Cached automatically
462462

463463
Owlery-based queries (`ImagesNeurons`, `NeuronsPartHere`, `PartsOf`, ...) are cached in two layers: the
464464
finished result (`images_neurons`, ...) and, underneath it, the Owlery id list (`owlery_ids`, Solr docs
465-
`vfb_query_owlery_ids_<term>_<c|i>_<hash>`). Until v1.22.58 `force_refresh` cleared only the result and then
465+
`vfb_query_owlery_ids_<term>_<c|i>_<hash>`). Before the fix on branch `fix/force-refresh-reaches-owlery-ids`, `force_refresh` cleared only the result and then
466466
recomputed it from the still-cached id list, so a refresh after a data load (new neurons) returned exactly the
467467
same stale set ("Force refresh requested ... Cache hit for owlery_ids" in the server log; seen 2026-10-12 on
468468
`ImagesNeurons(FBbt_00040051)`: 2678 cached, 3206 live). A forced call now raises a context flag

0 commit comments

Comments
 (0)