* follow-up: can't get any fsck msgid to fire for tags
@ 2023-08-01 16:13 Xavier Morel
0 siblings, 0 replies; only message in thread
From: Xavier Morel @ 2023-08-01 16:13 UTC (permalink / raw)
To: git
Following the previous investigation of commits I figured I'd look at
tags, and I'm wondering if I'm doing something wrong because going
down the list I attempted to trigger 5 fsck diagnostics and got 0 to
work.
My process is simple: create a loose object with an error in it e.g.
object 00
type blob
name bad
tagger a <a> 0 +0000
msg
which has an invalid sha1 reference for the object and thus seems like
it would trigger badObjectSha1[0].
Then run fsck on that object, enabling the msgid if it defaults to
IGNORE or INFO, and look at the result.
- badObjectSha1: error in git show (fatal: bad object), fsck says
"object could not be parsed" and "object missing"
- badTagName: the diag doesn't trigger at all
- badType: does error with "unknown tag type" (followed by "could not
be parsed" and "object missing") but the msgid is never listed so I
don't think this is from fsck
- extraHeaderEntry: "object could not be parsed" and "object missing"
(also "bad object" from "git show", despite extraHeaderEntry being
ignore by default so that's quite strange)
- missingObject: "object could not be parsed" and "object missing"
I'm really confused at this point.
Note: creating a ref for the annotated tag and fsck-ing the entire
repository sometimes generates different but not materially
better errors.
[0] https://git-scm.com/docs/git-fsck#Documentation/git-fsck.txt-codebadObjectSha1code
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2023-08-01 16:13 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2023-08-01 16:13 follow-up: can't get any fsck msgid to fire for tags Xavier Morel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).