<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/reftable/readwrite_test.c, branch gitk-resize-error</title>
<subtitle>Fork of git SCM with my patches.</subtitle>
<id>http://git.kilabit.info/git/atom?h=gitk-resize-error</id>
<link rel='self' href='http://git.kilabit.info/git/atom?h=gitk-resize-error'/>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/'/>
<updated>2021-12-23T20:28:34Z</updated>
<entry>
<title>reftable: signal overflow</title>
<updated>2021-12-23T20:28:34Z</updated>
<author>
<name>Han-Wen Nienhuys</name>
<email>hanwen@google.com</email>
</author>
<published>2021-12-23T19:29:49Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=0dd44584abf3fee0ba19b5edf856be2a79974228'/>
<id>urn:sha1:0dd44584abf3fee0ba19b5edf856be2a79974228</id>
<content type='text'>
reflog entries have unbounded size. In theory, each log ('g') block in reftable
can have an arbitrary size, so the format allows for arbitrarily sized reflog
messages. However, in the implementation, we are not scaling the log blocks up
with the message, and writing a large message fails.

This triggers a failure for reftable in t7006-pager.sh.

Until this is fixed more structurally, report an error from within the reftable
library for easier debugging.

Signed-off-by: Han-Wen Nienhuys &lt;hanwen@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>reftable: reftable file level tests</title>
<updated>2021-10-08T17:45:48Z</updated>
<author>
<name>Han-Wen Nienhuys</name>
<email>hanwen@google.com</email>
</author>
<published>2021-10-07T20:25:09Z</published>
<link rel='alternate' type='text/html' href='http://git.kilabit.info/git/commit/?id=ffc97f1a9e154262ae23bf2d6ec6c1541fa3b15a'/>
<id>urn:sha1:ffc97f1a9e154262ae23bf2d6ec6c1541fa3b15a</id>
<content type='text'>
With support for reading and writing files in place, we can construct files (in
memory) and attempt to read them back.

Because some sections of the format are optional (eg. indices, log entries), we
have to exercise this code using multiple sizes of input data

Signed-off-by: Han-Wen Nienhuys &lt;hanwen@google.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
