Skip to content

v0.1.3: Region-ordering guard, configurable variant batch cap, exact-position triage coverage

Choose a tag to compare

View all tags
@cyanheads cyanheads released this 28 Jun 13:59
v0.1.3
This tag was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.
7a09dc5
This commit was signed with the committer’s verified signature.
cyanheads Casey Hand
SSH Key Fingerprint: lkZCAfVCK5qsrcvEYCs0BnVRDCX7pKsdCZkw5yYKMuw
Verified
Learn about vigilant mode.

Region-ordering guard, configurable variant batch cap, exact-position triage coverage

Fixed:

  • gnomad_get_coverage / gnomad_list_gene_variants — an inverted region (start > stop) is rejected immediately as a ValidationError (reason: invalid_region, non-retryable) before any upstream call, instead of burning the retry budget on gnomAD's HTTP 500 and surfacing a misleading "unavailable" error; a single position (start == stop) stays valid (#1)
  • gnomad_get_variant — GNOMAD_MAX_VARIANT_BATCH now drives the batch cap (was hard-coded 25): the configured value flows into the advertised variants.maxItems, parse-time validation, and the description prose (#4)
  • gnomad_variant_triage — the callability step confirms the exact variant position (single-position region from a chrom-pos-ref-alt, or the resolved variant_id for an rsID) instead of gene-level coverage; dataset values are quoted in every tool-call example (#6)

99 tests pass; bun run devcheck clean.

Assets 3
Loading