Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • B baobaxia
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 67
    • Issues 67
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • 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
  • Wiki
    • Wiki
  • External wiki
    • External wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • NPDD
  • baobaxia
  • Issues
  • #143

Closed
Open
Created Apr 12, 2015 by Vince Tozzi@vinceOwner

JSON validation error when reading tags

Created by: agger-magenta

Sometimes, the output from git annex metadata --json produces JSON that fails to parse.

Like this:

{"command":"metadata","file":"dpadua/imagem/15/02/08/ocupacao-do-mercado-sul-de-taguatinga-bdab9.jpg",,"note":"","success":true}

The problem is the the empty element denoted by two commas in a row. I think we mainly see this problem in cases where there isn't actually any metadata, thus no tags either.

Maybe we should detect that empty element. Alternatively, we can parse the standard, non-JSON output instead.

Assignee
Assign to
Time tracking

Data Center Comunitário Livre - DCCL