Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • B Bio-DB-HTS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • ensembl-gh-mirror
  • Bio-DB-HTS
  • Merge requests
  • !41

Treat s3:// urls as remote as htslib 1.3 onwards supports it

  • Review changes

  • Download
  • Patches
  • Plain diff
Closed Marek Szuba requested to merge github/fork/Congenica/feature/support_s3 into master Jun 15, 2017
  • Overview 10
  • Commits 1
  • Pipelines 0
  • Changes 2

Created by: ah19

I've only added a super basic test for the method I changed rather than for the underlying s3 behaviour, I wasn't sure if you'd want a test going out to s3 as it might be flaky.

I've manually verified against htslib 1.3.2 that this does retrieve reads (via get_features_by_location) from a bam file in s3

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/Congenica/feature/support_s3