{"thread":{"id":"60050","subject":"follow-up: can't get any fsck msgid to fire for tags","startedAt":"2023-08-01T16:13:23Z","lastAt":"2023-08-01T16:13:23Z","messageCount":1,"participants":["Xavier Morel"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"480051","messageId":"086FB120-911A-4660-8964-3CD585442049@masklinn.net","threadId":"60050","inReplyTo":null,"subject":"follow-up: can't get any fsck msgid to fire for tags","fromName":"Xavier Morel","fromEmail":"xavier.morel@masklinn.net","sentAt":"2023-08-01T16:13:07Z","receivedAt":"2023-08-01T16:13:23Z","isPatch":false,"sender":{"key":"xavier.morel@masklinn.net","avatar":null},"body":"Following the previous investigation of commits I figured I'd look at\ntags, and I'm wondering if I'm doing something wrong because going\ndown the list I attempted to trigger 5 fsck diagnostics and got 0 to\nwork.\n\nMy process is simple: create a loose object with an error in it e.g.\n\n    object 00\n    type blob\n    name bad\n    tagger a <a> 0 +0000\n\n    msg\n\nwhich has an invalid sha1 reference for the object and thus seems like\nit would trigger badObjectSha1[0].\n\nThen run fsck on that object, enabling the msgid if it defaults to\nIGNORE or INFO, and look at the result.\n\n- badObjectSha1: error in git show (fatal: bad object), fsck says\n  \"object could not be parsed\" and \"object missing\"\n- badTagName: the diag doesn't trigger at all\n- badType: does error with \"unknown tag type\" (followed by \"could not\n  be parsed\" and \"object missing\") but the msgid is never listed so I\n  don't think this is from fsck\n- extraHeaderEntry: \"object could not be parsed\" and \"object missing\"\n  (also \"bad object\" from \"git show\", despite extraHeaderEntry being\n  ignore by default so that's quite strange)\n- missingObject: \"object could not be parsed\" and \"object missing\"\n\nI'm really confused at this point.\n\nNote: creating a ref for the annotated tag and fsck-ing the entire\nrepository sometimes generates different but not materially\nbetter errors.\n\n[0] https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-codebadObjectSha1code"}]}