Repository navigation
deps: update ghcr.io/hassansaei/vntyper docker tag to v2.0.50 - #459
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
2.0.47→2.0.50Release Notes
hassansaei/VNtyper (ghcr.io/hassansaei/vntyper)
v2.0.50Compare Source
Deployment to vntyper.org is deliberately deferred. VNtyper-Online stays on 2.0.47; vntyper-online-backend keeps its 2.0.47 digest pin.
Image:
ghcr.io/hassansaei/vntyper:2.0.50@sha256:d9cd90cd1b717d6c5fcebf3ce09d37ec4e86b4a6dc23074bb0b2bdce5af0e21c(revisiond260faf). PyPI:vntyper==2.0.50.Web service: anonymous research donations
vntyper-donation/2:POST /donations/takes a JSON record of enums, bins and booleans (no file, no run ID, no sample name, no hashes), refuses extra fields (422), non-JSON bodies (415), bodies over 2 KB (413) and answers 403 whileENABLE_DONATIONSis off. The response is{"status": "recorded"}; no identifier is returned or stored.donations_v2with the whitelisted fields, a server-sidereceived_quarterand a random key. The v1donationstable, the archive validation and the integrity check on donated ZIPs are removed. With donations enabled the API refuses to start without a reachablePOSTGRES_URLinstead of falling back to an in-memory store./donations/aggregates/returns counts only,nullbelow k=5 (k=10 for confirmed positives and tool calls), with complementary suppression./donations/, and a rate-limited donation request is logged without the client address. In production a missingPSEUDONYM_SECRETis now logged as an ERROR at startup of the API and every worker.docker/apponly.v2.0.49: VNtyper v2.0.49Compare Source
Deployment to vntyper.org is deliberately deferred. The manuscript revision and VNtyper-Online stay on 2.0.47; vntyper-online-backend keeps its 2.0.47 digest pin.
Image:
ghcr.io/hassansaei/vntyper:2.0.49@sha256:9144f02d1302f8132b13a7a42b026307759594bd08020c1ab850cc7dc9aa3e76(revision7135a19). PyPI:vntyper==2.0.49.Runtime
--threads(at most 4); the total never exceeds--threadsand the k-mer count file is byte-identical for every split. On an exclusive Xeon E5-2667 v4 node with a 1.25 GB BAM, normal mode runs 13% faster at 8 threads and 31% faster at 4; KAnalyze peak memory rises from 3.3 to 5.6 GB at 8 threads, inside the existing 12 GB Java heap.v2.0.48: VNtyper v2.0.48Compare Source
Deployment to vntyper.org is deliberately deferred. The manuscript revision and VNtyper-Online stay on 2.0.47; vntyper-online-backend keeps its 2.0.47 digest pin. Before any later deployment, set one stable
PSEUDONYM_SECRETon the API and every worker (#355).Image:
ghcr.io/hassansaei/vntyper:2.0.48@sha256:451797a6523b8ef12b48e7d57d596971336b29953f05811a6163f5e36fcd3689(revision156c6f5). PyPI:vntyper==2.0.48.Vrbacká 2025 citation and published variant names (decision profile revision 3)
known_variantsciteddoi:10.1101/2024.11.14.623419, an unrelated preprint. It now citesdoi:10.1101/2025.09.06.673538.53_54insGand53_54insAbecome54_55insGand54_55insA;57_58insG, the same allele as58_59insG, is removed and58_59insGcites Olinger 2020 and Vrbacká 2025;54dupG, not in the paper's Table 1, is removed.known_variantsdecides Tier A eligibility, so the packaged profile moves to revision 3. Summaries recorded with revision 2 (2.0.1 to 2.0.47) are still accepted byvntyper cohort.57_58insG,53_54insG,53_54insAor54dupGis nowrepresentation-of-caller-callinstead ofknown-variantand cannot reach Tier A. On the development simulation 37 rows change only their nomenclature flags and note; no name, tier or call changes. Caller thresholds and screening messages are unchanged.Web service: job timing, job summary and keyed pseudonyms
/job-status/{id}/also returnssubmitted_at,started_atandcompleted_at(ISO 8601 UTC,nullwhen not recorded).GET /job-summary/{id}/(#355): returns the run's ownpipeline_summary.jsonfrom the result archive, with the same identifier check, rate limit, file-safety rules and retention as/download/.PSEUDONYM_SECRET. Set one stable value on the API and every worker; unset, each process uses a random key and logs a warning, so unique-user counts overcount. Existing hashes and pseudonyms do not carry over.docker/apponly.Cohort discovery and input errors
vntyper cohortfollows directory symlinks below an input root (each real directory once) and logs every directory it cannot read. Before Python 3.13 the recursive search skipped both without a word, so completed samples were missing from the exports.--reference-assembly, a blank or failed library), instead of claiming that reads would be dropped.Test suite
Subthreshold note covers dupC candidates
ALT == alt_filtering.gg_alt_value) below the reporting floor also failsalt_filter_pass, because the shippedgg_depth_score_thresholdequals the floor, so it never qualified for the subthreshold note. Such a row now qualifies when its ALT failure is the GG depth rule alone. Those no-call samples now carry the note and thenegative_subthresholdstate. Excluded ALTs and artifact-flagged rows stay ineligible. A dupC row at or above the floor that fails only a stricter custom GG threshold is not subthreshold.Grade and subthreshold state in machine-readable outputs
pipeline_summary.json(#356): recordsconfidence_grade, the grade the report prints, andsubthreshold_signalwithstate(negative_subthresholdornone),best_depth_score,event_countandsupport_count. The report computes both and re-anchors the summary before rendering, so the printed integrity digest covers them.vntyper reportnever rewrites a supplied summary.kestrel/subthreshold_signal.json; the##line inkestrel_result.tsvis unchanged.cohort_stats.csv,.tsvand.jsonappendconfidence_grade,subthreshold_state,subthreshold_best_depth_score,subthreshold_event_countandsubthreshold_support_countafter the existing columns. Summaries written before this release give empty cells.🤖 Generated with Claude Code
Configuration
📅 Schedule: (UTC)
* 0-5 * * 1)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.