TVO-CONFLICT-019: Merge fell back to the byte level: a contributing commit has no captured line-ops

If this error reveals a permission or cryptography flaw, do not post it — follow coordinated disclosure. Do not report security vulnerabilities here. This board is public and operated by a third-party vendor. Read https://tovio.dev/security and use the private channel it names. Never paste repository contents, file paths, diffs, tokens, keys, or other people's data — describe the behaviour instead.

What TOVIO prints

The catalog's example of what TOVIO prints for this code in a terminal. Names, paths and counts in it are illustrative.

⚠ 1 conflicted path(s) merged without accumulated line attribution
    ~ src/integrations/cgm/dexcom.ts  (ours unattributed)
  a contributing commit carries no usable captured line-ops there, so the byte-level merge decided the path
  — accumulated attribution on both sides may well have merged it cleanly
  see what decided each path:  tovio explain merge feature/cgm-sync --into main
  resolve the conflicts:       tovio resolve
  a binary, oversized, protected or legacy side records nothing by design, and neither does a commit replayed
  by `change rebase`/`cherry-pick`/`revert`/`split`/`absorb` — no setting would have caught any of them
  `[line_ops] strict = true` refuses only a plain `tovio commit` that failed to describe an ELIGIBLE file
  — it does not reach any of the causes above
  [TVO-CONFLICT-019]

What to read

• Error reference — the three-part message standard (what happened, why, what to do next), the exit-code classes, the --json shape, and the everyday codes. It is a curated subset, so it may not name this one: TVO-CONFLICT-019 is in the CONFLICT area and carries the same three-part message either way.
• Troubleshooting — the diagnostic commands and recovery paths behind the most common failures.

Still stuck, or is the message wrong?

Report it. The link carries only this code and the surface; describe the behaviour in your own words and never paste secrets, capability tokens, session strings, or private repository data.

Report this error

All error codes