GitoxideLabs/gitoxide gix-features-v0.49.0

gix-features v0.49.0

on GitHub

Bug Fixes

• report the error that caused in_parallel_with_slice() to stop
  Previously, when a consumer failed, worker threads were joined in
  thread-id order and the first error encountered was returned. Threads
  that merely noticed the stop signal can bail out with a reactive error
  like Interrupted though, and when such a thread had a lower id than
  the failing one, that reaction would mask the actual cause of the stop.

  Now the first consumer to fail owns the causal error, and it is
  preferred over reactive errors when the join results are collected.
  Causality is tracked on a flag private to the harness as consumers may
  set the exposed stop flag themselves before returning their error.

  This makes the error of Tree::traverse() in gix-pack deterministic,
  and with it the previously intermittent assertion on OutOfMemory in
  bundle::write_to_directory::respects_alloc_limit_bytes (#2701).

• keep the underlying zlib error when decompression fails
  Previously, every decompression failure was flattened into the fixed
  "corrupt deflate stream" message, making a checksum failure
  indistinguishable from genuine bitstream corruption even though zlib
  knows the difference. As reported in #2703, this cost real debugging
  time downstream when a checksum bug in the aarch64 NEON path of
  zlib-rs made a valid pack look corrupted.

  Now Decompress exposes the message of the last error, and the inflate
  stream appends it, turning the error into something like
  "corrupt deflate stream: incorrect data check".

Chore (BREAKING)

• remove zlib module in favor of standlone gix-zlib.
  This also removes the previously deprecated zlib-related features.

Commit Statistics

• 14 commits contributed to the release.
• 58 days passed between releases.
• 3 commits were understood as conventional.
• 1 unique issue was worked on: #2703

Commit Details