Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • VTK VTK
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 733
    • Issues 733
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 203
    • Merge requests 203
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • VTK
  • VTKVTK
  • Issues
  • #18150

Closed
Open
Created Mar 14, 2021 by Utkarsh Ayachit@utkarsh.ayachit⛰Owner

CompositeDataSetRange does not work correctly for AMR

CompositeDataSetRange has potentailly access flat index for an iterator location at the end. This is invalid and not uspported for AMR, causing issues. See !7745 (merged)

Assignee
Assign to
Time tracking