Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.core beat.core
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beatbeat
  • beat.corebeat.core
  • Issues
  • #28
Closed
Open
Issue created Mar 19, 2015 by André Anjos@andre.anjos💬Owner

No way to visualise (binary) cache data

After our data re-structuring in this package, a useful feature was removed: the ability to write cache files as JSON text. Cache files are now written in binary format, which improves the calculation precision and translates to what happens inside the platform. It is also much faster.

A side effect was we lost the possibility to directly view cache files.

A command-line option/command at our beat swiss-army knife could allow us to recover this ability, by providing a "view" command that allows one to inspect the contents of binary cache files.

This bug will remain opened until this is fixed.

Assignee
Assign to
Time tracking