Repository navigation
taxify 0.5.2
A follow-up audit for the shape behind #55: a failure returned as a plausible
answer, with the only notice gated on verbose.
The cause behind #55 does not recur
Every other session cache is keyed on a backbone name or a file basename, both
bounded by construction; taxifydb has no environment caches at all. A scale
sweep over taxify(), add_trait(), add_gift(), add_wcvp(),
add_common_names(), add_classification(), add_iucn(), inspect() and
reconcile() at 5 / 100 / 800 / 2400 names confirms every count now grows with
the batch.
The shape, though, was in three more places
-
region =/coords =now warn when the constraint could not be applied.
With no range data for the declared region,region_range_sets()returned
NULLand the fuzzy filter passed its candidates through unconstrained, so a
match the region would have excluded could win. This is the one that could
change which taxon a name resolved to. -
inspect()names the checks it could not run, in the report header under
not checked. An anomaly-only report has no other way to separate a check
that ran clean from one that never ran: both contribute no rows, and the
report then prints "nothing stood out". The genus-recognition check without
the register, and both range checks without the WCVP range data, were skipped
that way. The skipped set travels on the result, so a saved report carries it. -
Cross-backbone name recovery names a backbone it could not resolve
against, instead of silently contributing no alternatives for it. That pass
runs over the whole gap set at once, which is where a size-dependent failure
like #55 would next hide.
Deliberately left alone
Verified as not the same shape: the xdelta3 patch fallback and the
point-in-polygon engine fallback (both compute the same answer another way),
the "already present (pinned)" notices (successes), add_combine()'s degrade to
reported-only (documented, with per-cell _src provenance), and the authorship
tiebreak (the row stays flagged ambiguous).