Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • E ensembl-otter
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Jira
    • Jira
  • Merge requests 3
    • Merge requests 3
  • 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
  • ensembl-otter
  • Merge requests
  • !116

Processing case with only one locus entry

  • Review changes

  • Download
  • Patches
  • Plain diff
Merged Marek Szuba requested to merge Bugfix/ClonesLocusError into master Jun 11, 2020
  • Overview 0
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: mira13

When we got only one locus entry, it is not on the second level of hash, but on first, without name key. FIxed with converting to expected hash. Issues 3478, 3454, 3403

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: Bugfix/ClonesLocusError