kc3-lang/libgit2

Branch :


Log

Author Commit Date CI Message
0551dfd4 2026-08-15 13:37:11 Merge pull request #7346 from weihanglo/zstream-infloop fix(zstream): fail on truncated input instead of looping forever
0334930c 2026-08-15 13:35:47 Merge pull request #7341 from karpovantonme/docs/param-names-match-signatures docs: fix six @param names that do not match the signatures
0b87f30b 2026-08-13 21:58:29 Merge pull request #7347 from sgallagher/cve_2026_5917 CVE-2026-5917: Escape repo path in gen_proto()
5948ef38 2026-08-13 13:48:38 CVE-2026-5917: Escape repo path in gen_proto() Takes inspiration from 346f28b89d6aae0c3ea0b9f0b0bc0f0afa177fab Signed-off-by: Stephen Gallagher <sgallagh@redhat.com>
d5354500 2026-08-12 08:34:46 test(odb): reads of truncated loose objects fail This ensure that `git_odb_read` fails when reading truncated loose object. If you move this before the fix commit, this loops forever
1c1ba2e7 2026-08-12 08:33:10 test(zstream): reject truncated zlib streams When inflating a stream, if the stream is truncated midway, it must fail rather than loop forever.
5254f5dc 2026-08-12 08:32:40 fix(zstream): fail on truncated input instead of looping forever `inflate()` reports `Z_BUF_ERROR` when a truncated stream exhausts its input before reaching `Z_STREAM_END`. The stock `zstream_seterr` suggests treating that as non-fatal so callers can retry with more input or output space. However, the drain loop in `git_zstream_get_output` can supply neither because * output space is still available * input is only refilled outside the loop It would leads to zero-progress forever. The problematic behavior was found in `git_odb_read` on a truncated loose object. The proposed fix here: Detect the stuck state in the drain loop and report an error.
b0057d0f 2026-08-12 21:18:11 Merge pull request #7344 from yvonnelxxxx/fix/signed-int-overflow-config-parse-int64
1e9bbdc0 2026-08-12 16:16:06 fix signed-int-overflow inconfig_parse_int64
95ff8c2b 2026-08-11 17:13:20 Merge branch 'ethomson/reftable_build' into main