Skip to content

fix(ENGKNOW-3046): enable cram binding to correct reference genome for exome cloud bfx#103

Merged
gmagnu merged 8 commits intomainfrom
ENGKNOW-3046-enable-cram-binding-to-correct-reference-genome-for-exome-cloud-bfx
Feb 5, 2026
Merged

fix(ENGKNOW-3046): enable cram binding to correct reference genome for exome cloud bfx#103
gmagnu merged 8 commits intomainfrom
ENGKNOW-3046-enable-cram-binding-to-correct-reference-genome-for-exome-cloud-bfx

Conversation

@gmagnu
Copy link
Contributor

@gmagnu gmagnu commented Feb 5, 2026

No description provided.

@gmagnu gmagnu changed the title Engknow 3046 enable cram binding to correct reference genome for exome cloud bfx fix(ENGKNOW-3046): enable cram binding to correct reference genome for exome cloud bfx Feb 5, 2026
@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Junit Tests - Summary

4 411 tests  ±0   4 239 ✅ ±0   11m 32s ⏱️ + 1m 18s
  462 suites  - 1     172 💤 ±0 
  462 files    - 1       0 ❌ ±0 

Results for commit 7057e6d. ± Comparison against base commit d44ae4b.

♻️ This comment has been updated with latest results.

…e-cram-binding-to-correct-reference-genome-for-exome-cloud-bfx

# Conflicts:
#	gortools/src/test/java/gorsat/UTestCram.java
#	model/src/main/java/org/gorpipe/gor/driver/providers/stream/datatypes/cram/CramIterator.java
#	model/src/main/java/org/gorpipe/gor/driver/providers/stream/datatypes/cram/reference/EBIReferenceSource.java
#	model/src/main/java/org/gorpipe/gor/driver/providers/stream/datatypes/cram/reference/FolderReferenceSource.java
#	model/src/main/java/org/gorpipe/gor/driver/providers/stream/datatypes/cram/reference/MD5CachedReferenceSource.java
@gmagnu gmagnu merged commit 74206cd into main Feb 5, 2026
11 checks passed
@gmagnu gmagnu deleted the ENGKNOW-3046-enable-cram-binding-to-correct-reference-genome-for-exome-cloud-bfx branch February 5, 2026 16:13
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.

2 participants