Truthound · All articles · 15/24
Evidence-led Truthound Core guidance on data contracts, check inputs and operational limits.
480 articles
Dask array conversion after Parquet projection: align partition and length-vector units
Projection can combine partitions in the execution graph, so align declared partition metadata with the length vector’s actual ownership unit.
True in a Dask object column: identical text is not an identical Boolean state
Use original value types and missingness semantics as the handoff contract rather than display text.
Passing a uint8 mask through Dask: separate creation from completed deserialization
Check dtype and fill semantics through a real serialization roundtrip.
Dask masked scalar arithmetic: hand off graph dtype and computed dtype together
Reconcile actual masked-array scalar promotion with graph inference.
171 versus 13 in Dask loc: do not force an index mask into positional alignment
Check partition correspondence of the data and index mask at the execution boundary.
Dask map_overlap chunks=None: verify that the next team receives known chunk sizes
Check actual chunk knowledge rather than treating omitted and explicit None options as equivalent.
Do not interpret a nonfinite singleton variance as stable zero
Keep the population-variance result of a non-finite singleton separate from a finite singleton's no-variation state. Retain input classes and result tags so indeterminate arithmetic is not published as a stability metric.
Keep a target type for all-NULL Parquet struct children in DuckDB
Establish cast completion before checking the returned type and NULL positions of a NULL-only struct child. An invalidated connection is not a successfully typed missing-value result.
Declare timestamp precision before a DuckDB Parquet glob chooses it
Compare actual timestamp values when changing the first file in a glob. An output dtype alone can make already-rounded timestamps appear acceptable.
Check NaN constants before treating negated DuckDB comparisons as algebra
Reconcile row-selection flags for the original negated comparison and its optimized path when NaN is present. Quarantining every non-finite value does not establish that the original predicate was preserved.
Distinguish a NULL aggregate row from no row in DuckDB
Check a NULL aggregate value separately from the absence of its result row on empty input. Retain controls for correlation and DISTINCT so missing-value handling cannot hide a cardinality error.
Compare DuckDB DESCRIBE aliases with actual output headers
For a quoted alias, compare DESCRIBE names with execution headers while preserving case. Lowercasing during extraction can erase a schema discrepancy that changes the consumer contract.
Choose the survivor before relying on DuckDB INSERT OR IGNORE
For a batch with intersecting UNIQUE constraints, successful insertion leaves the winner question open. Define the survivor policy first, then approve INSERT OR IGNORE against the selected key set.
Restore expression objects before accepting a DuckDB export as recoverable
Restore schemas containing COLLATE and subscripts into a separate database. Distinguishing export completion, SQL parse success, and restored values identifies the first failing recovery boundary.
Cross platform and list-length boundaries for DuckDB BIGNUM lambdas
A scalar control is insufficient to approve lambda comparisons involving a large negative number. Check result Booleans across list lengths and element positions on the operating system that will run the query.
Check Doris VARIANT field presence when UTC Z parsing depends on aliases
After loading a Zulu timestamp, check presence and non-null state at the typed VARIANT path even if the row succeeded. Record the BE conversion context without treating later host state or a compaction observation as proof of cause.
Keep net-zero rewrites from erasing a Doris offset snapshot key
A same-value rewrite can still require the earlier row in an offset-based snapshot. Test the effect of net-delta elimination against keys fixed at that offset while preserving the report's unexecuted-scenario scope.
Wait for Doris load visibility across a schema-change barrier
Link COMMITTED loads to visible keys before announcing completion during a schema change. Investigate transaction and version traces instead of treating a visibility timeout as an automatic reason to reload.
Check the logical slice boundary before subtracting a Doris read offset
Check the logical slice boundary before relying on the enclosing packed object's size. Separate direct-reader and cache-protected paths when investigating an out-of-range offset.
Use one metadata snapshot before deleting a Doris packed slice
Build packed-slice deletion candidates from every page of formal, recycle, and temporary references at one snapshot. Absence in inventories captured at different times does not establish absence overall.
