Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • YARR YARR
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 41
    • Merge requests 41
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • YARR
  • YARRYARR
  • Issues
  • #150
Closed
Open
Created Apr 29, 2022 by Timon Heim@theimOwner

Scan progress monitor

Currently there is no clear strategy how to monitor the progress of a scan. We are relying on printouts from loops, which is up to developers to determine and is not very clean for all potential use cases/scans.

A long time ago I experimented with a progress monitor system which uses the LoopStatus from the scan engine to report the progress in form of a simple progress bar. This worked but can be messy when combined when other printouts.

There is this solution for spdlog, which might be interesting: https://github.com/michalber/spdmon

Cheers, Timon

Assignee
Assign to
Time tracking