Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • 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
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 6
    • Issues 6
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Jira
    • Jira
  • Merge requests 0
    • Merge requests 0
  • Requirements
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
    • Value stream
  • 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

Closed
Created Jun 15, 2017 by Marek Szuba@mks
  • Report abuse
Report abuse

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

  • Overview 10
  • Commits 1
  • 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
Reviewer
Request review from
Time tracking
Source branch: github/fork/Congenica/feature/support_s3