Skip to content

Comments

Fix truthiness bug in region boundary checks — use is not None instead of boolean evaluation#941

Open
blankirigaya wants to merge 1 commit intomalariagen:masterfrom
blankirigaya:fix/region-truthiness-check
Open

Fix truthiness bug in region boundary checks — use is not None instead of boolean evaluation#941
blankirigaya wants to merge 1 commit intomalariagen:masterfrom
blankirigaya:fix/region-truthiness-check

Conversation

@blankirigaya
Copy link
Contributor

Fixes #940 .

0 is a valid genomic start coordinate but is falsy in Python. All 7 region boundary checks of the form if region.start or region.end would skip slicing when start=0, silently returning the entire contig.

Changed all 7 instances to if region.start is not None or region.end is not None, which correctly distinguishes between "no boundary specified" and "boundary is zero".

Files changed: snp_data.py (lines 244, 344, 497, 661, 1134), hap_data.py (lines 146, 388).
Testing: Existing tests should be supplemented with cases where region.start=0 to cover this boundary condition — these would have passed incorrectly before this fix.

Replace if region.start or region.end: with
if region.start is not None or region.end is not None: across 7
locations in snp_data.py (5) and hap_data.py (2).

Python treats 0 as falsy, so the old check would skip region slicing
when start=0, returning the entire contig instead of the requested
region — a silent data-correctness bug.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

if region.start or region.end silently returns entire contig when start=0

1 participant