{"record":{"id":"54f9723359c9a11c","repo":"GitoxideLabs/gitoxide","slug":"lines-in-could-not-be-parsed","errorCode":null,"errorMessage":"{} lines in '{}' could not be parsed","messagePattern":"(.+?) lines in '(.+?)' could not be parsed","errorType":"exception","errorClass":null,"httpStatus":null,"severity":"error","filePath":"gitoxide-core/src/mailmap.rs","lineNumber":39,"sourceCode":"    let mut seen = HashSet::<(_, _)>::default();\n    for entry in gix::mailmap::parse(&buf).filter_map(Result::ok) {\n        if !seen.insert((entry.old_email(), entry.old_name())) {\n            writeln!(\n                out,\n                \"NOTE: entry ({:?}, {:?}) -> ({:?}, {:?}) is being overwritten\",\n                entry.old_email(),\n                entry.old_name(),\n                entry.new_email(),\n                entry.new_name()\n            )?;\n        }\n    }\n\n    if err_count == 0 {\n        writeln!(out, \"{} lines OK\", gix::mailmap::parse(&buf).count())?;\n        Ok(())\n    } else {\n        bail!(\"{} lines in '{}' could not be parsed\", err_count, path.display());\n    }\n}\n","sourceCodeStart":21,"sourceCodeEnd":42,"githubUrl":"https://github.com/GitoxideLabs/gitoxide/blob/e73179060badf27222d790981fac3f84c1830a7e/gitoxide-core/src/mailmap.rs#L21-L42","documentation":"Reported at the end of `mailmap::verify`, which parses a mailmap file and counts entries that `gix::mailmap::parse` failed to parse. After streaming all entries, if `err_count > 0` the function returns this error naming how many lines were unparseable and which mailmap file they came from. It fires when the mailmap file contains lines that don't match git's mailmap syntax (e.g. malformed `Proper Name <email>` forms, missing brackets, stray tokens). The function also prints OK-line counts and overwrite notes to `out` while collecting errors, so this error signals a partially invalid user-supplied mailmap that needs manual correction.","triggerScenarios":"Running mailmap verification against a `.mailmap` file containing syntactically invalid entries - e.g. malformed `Proper Name <email> <commit-email>` lines - causing `gix::mailmap::parse` to emit errors.","commonSituations":"Hand-edited mailmap files with typos (missing angle brackets, stray characters); merge conflicts in .mailmap left partially resolved; copied mailmap snippets with wrong formatting.","solutions":["Inspect each malformed line reported and fix its syntax per git mailmap format (`Name <proper@email> <commit@email>`)","Check for leftover merge-conflict markers in the file","Re-run `gix mailmap verify` until it reports all lines OK"],"exampleFix":"// before (.mailmap)\nJohn Doe john@example.com johnny\n// after (.mailmap)\nJohn Doe <john@example.com> <johnny@example.com>","handlingStrategy":"validation","validationCode":null,"typeGuard":null,"tryCatchPattern":"if let Err(e) = mailmap::verify(&path, format, &mut out) {\n    eprintln!(\"mailmap check failed: {e}\");\n}","preventionTips":["Validate .mailmap syntax after every edit","Run verify as part of CI on repositories with mailmaps"],"tags":["git","mailmap","parse-error","validation"],"backgroundTag":"schema-validation-failed","analyzedSha":"e73179060badf27222d790981fac3f84c1830a7e","analyzedAt":"2026-09-08T11:26:50.865Z","contentChangedAt":"2026-09-08T11:26:50.865Z","schemaVersion":2},"datasetVersion":"2026-09-15T23:17:13.987Z"}