Truthound · All articles · 18/24
Evidence-led Truthound Core guidance on data contracts, check inputs and operational limits.
480 articles
Polars strict struct casts: check field sets and order instead of success alone
Do not assume strict rejects the same schema changes on every path. Compare the actual nested structure.
Polars row-oriented Boolean conversion: should raw 2 become false?
Validate the allowed raw integers and conversion policy, not just the final Boolean dtype.
Validating distinct counts after variable-offset Polars rolling slices
A selected sequence can lose its original sort order even when cached metadata says otherwise.
Polars is_in pushdown: checking filter meaning for nulls and negative zero
Compare inclusion decisions for original rows when checking filter equivalence across execution backends.
Duplicate Polars Map keys: when lookup and dictionary conversion choose different values
Define key uniqueness within each parent row and an explicit duplicate policy before consumers choose different Map operations.
Polars literal-comparison length errors: verify the row-mask contract
Equivalent comparisons can take different scalar and row-wise paths. Check the boundary where the mask must be materialized.
Polars projection after left join_where: a correct column name can hide the wrong source
Distinct field markers and a complete schema check distinguish a wrong column value under a plausible name.
Checking Iceberg delete positions before trusting a head limit
A delete at position 100 cannot address a four-row file; validate the metadata before checking output size.
Polars group extrema after reverse: compare membership as well as the maximum
Separate reordering from selecting fewer elements before deriving an independent expected extreme.
Choosing a NaN policy before moving Polars comparisons to a GPU
When NaN > 0 selects different rows across engines, matching Boolean schemas are not enough.
Checking empty strings versus NULL across Polars CSV engines
Matching String dtypes do not establish that a quoted empty field retained its meaning.
Checking Delta deletion-vector references when encoded paths disagree
Separate object identity from deletion application when only escaped partition paths return deleted rows.
Checking Polars Decimal shift fill values when 1.25 becomes 0.01
Decimal accuracy in existing rows and scale conversion in newly filled rows are separate contracts.
Preserving parent validity when Polars Array extraction exposes zero
A child buffer value is not a valid measurement when its parent array row is NULL.
Polars argmax ties: the maximum can be correct while the selected row is wrong
A positional tie-breaking contract exposes selection errors that a value-only check cannot detect.
Check whether Iceberg WAP data is visible on main before approval
Actual branch visibility and the existence of the WAP snapshot define the approval boundary more clearly than a stage label.
Check that an Iceberg UUID composite delete is attached to scan tasks
A committed delete file can exist without reaching the reader's applicable scan plan.
Iceberg upserts after partition evolution: check updates and deletes of existing keys
Successful writes to a new partition spec do not establish that rows written under the old spec were removed.
Iceberg nested equality deletes: verify survivors as well as deletion targets
Preservation of nontarget rows is a separate acceptance condition, not an optional consequence of deleting the intended keys.
When Iceberg fixed-binary delete keys collapse, inspect buffer ownership
Compare the distinct keys written to the file with those retained in the reader's in-memory set.
