Patrick Steinhardt <ps@xxxxxx> writes: > yesterday I noticed that writing reftables with more than 250,000 refs > led to the last block of refs in the table not being seekable anymore. > As it turns out, 250k refs was the boundary at which we start to write > multi-level indices for refs. Obviously one of the less exercised corners of the code ;-) > The topic depends on Junio's jc/reftable-core-fsync at 1df18a1c9a > (reftable: honor core.fsync, 2024-01-23) due to a semantic merge > conflict in the newly added test. Thanks for the note for the base. John Cai's work is well done and has been reviewed, so let's merge it down to 'next' soonish. Thanks.
