Skip to content

Fix vcfnorm writing float missing values to wrong buffer#2522

Open
sirus20x6 wants to merge 1 commit intosamtools:developfrom
sirus20x6:fix/vcfnorm-split-format
Open

Fix vcfnorm writing float missing values to wrong buffer#2522
sirus20x6 wants to merge 1 commit intosamtools:developfrom
sirus20x6:fix/vcfnorm-split-format

Conversation

@sirus20x6
Copy link

Summary

  • In split_format_numeric, bcf_float_set_missing(src_vals[idst]) wrote to the source buffer instead of the destination — changed to dst_vals[idst] to match the int32 case on the preceding line

Test plan

  • Existing test suite passes (updated atomize.split.1.{0,1}.out for correct missing fields)
  • Verify splitting multiallelic float FORMAT fields (GL, GP) produces correct missing values

The BCF_HT_REAL case in split_format_numeric called
bcf_float_set_missing(src_vals[idst]) instead of
bcf_float_set_missing(dst_vals[idst]), writing the missing sentinel
into the source buffer rather than the destination. The int32 case on
the preceding line correctly uses dst_vals[idst].
@sirus20x6 sirus20x6 force-pushed the fix/vcfnorm-split-format branch from 29a8528 to be0b7ef Compare March 26, 2026 00:54
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.

1 participant