Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
VTK
VTK
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 561
    • Issues 561
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 145
    • Merge Requests 145
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • VTK
  • VTKVTK
  • Issues
  • #18069

Closed
Open
Opened Dec 23, 2020 by Ben Boeckel@ben.boeckelOwner

STLWriter error checking needs investigation

The vtkSTLWriter class tries to detect "out of space" errors, but does so poorly. It checks only fflush for an error (any error) and assumes it means ENOSPC (rather than checking for EIO or other plausible errors). The thing is that fwrite/fprintf could also have triggered the ENOSPC leaving nothing in the buffer to flush and therefore no error.

I've disabled the testing of the "out of space" error for now because the code just isn't handling the detection well enough for our CI.

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: vtk/vtk#18069