Re: [PATCH 4/7] reftable: avoid writing empty keys at the block layer
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Jan 14, 2022, 01:26 UTC
- Message-ID
- <xmqqpmovds5q.fsf@gitster.g>
- In-Reply-To
- <e4c1cc58265ca7ae7b32b9faf41324883011d1a6.1642010868.git.gitgitgadget@gmail.com>
"Han-Wen Nienhuys via GitGitGadget" <gitgitgadget@gmail.com> writes:
Show 13 quoted lines
> diff --git a/reftable/block_test.c b/reftable/block_test.c > index 4b3ea262dcb..5112ddbf468 100644 > --- a/reftable/block_test.c > +++ b/reftable/block_test.c > @@ -42,6 +42,11 @@ static void test_block_read_write(void) > header_off, hash_size(GIT_SHA1_FORMAT_ID)); > reftable_record_from_ref(&rec, &ref); > > + ref.refname = ""; > + ref.value_type = REFTABLE_REF_DELETION; > + n = block_writer_add(&bw, &rec); > + EXPECT(n == REFTABLE_API_ERROR); > +
The preimage of this hunk has been invalidated by your 9c498398 (reftable: make reftable_record a tagged union, 2021-12-22).
I see that the hn/reftable-coverity-fixes topic, which the commit is a part of, has been expecting a reroll since last year---are you plannning to rebuild that series after landing this series first?