Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • A ADIOS2
  • Project information
    • Project information
    • Activity
    • Labels
    • Planning hierarchy
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 9
    • Merge requests 9
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Podhorszki, Norbert
  • ADIOS2
  • Issues
  • #1309

Closed
Open
Created Mar 20, 2019 by Podhorszki, Norbert@pnbMaintainer

BP3: Put(Sync) triggering a Flush will mess up outstanding Spans

Created by: germasch

From looking at the code in BP3Writer.cpp, when preallocating a new Span would trigger a flush because the internal buffer reaches MaxBufferSize, the code will throw an exception as the flush will make it impossible to use outstanding Spans on the app side, as their data has already been written out -- using them after that time would corrupt whatever data is being buffered now.

However, PutSync can trigger a flush as well, causing the same issue, so I suppose it should also better throw an exception, as that's better than silent corruption.

Assignee
Assign to
Time tracking