Brad Larsen

Maybe relevant — a list of the various ways to configure proxies: https://gist.github.com/yougg/5d2b3353fc5e197a0917aae0b3287d64

P.S. `git fsck` reports no errors in the deqp.git repository. Additionally, it appears that the gitoxide panic occurs when trying to use `gix::Repository::find_object` with object ID `5665283d8c34f78a615fb6bf76fdd14bdb19b882`.

I'll open a PR for the error handling changes. I will also try reproducing with the older version before `96164c5` to see if I still have trouble there. But that's...

> Could you try to compile with an older version, one before 96164c5 (96164c5~1 == f3684a4f67f98c0e3884e2d348cb092f48ca443a) to see if this is still reproducible without zlib-rs? I tried this on my...

@Byron I opened a PR to make `gix_pack::data::delta::apply` a fallible function: #2059.

@Byron Let me try your `gix cat 5665283d8c34f78a615fb6bf76fdd14bdb19b882` test case on my x86_64 machine to see if I can reproduce it now, and perhaps put together a unit test. Like...

## x86_64 crash On my x86_64 system, with a fresh debug build of gitoxide commit 8007f1d0bad357688acd1235d079bf164290cda6: ``` % cargo run -- -r /disk2/deqp.git -v --trace cat 5665283d8c34f78a615fb6bf76fdd14bdb19b882 Finished `dev` profile...

To test whether the llvm / cargo / rust versions make a difference, I tested on the same x86_64 machine using the `rust:latest` Docker image. Same crash. ``` # rustc...

> I am pretty sure hope that if you would apply this patch and run it on an x86 machine, the last status would not be StreamEnd. > > Could...

Note that the `Encountered unsupported command code: 0` is being produced from `gix_pack::data::file::decode::entry::::resolve_deltas`. A stack trace from a copy modified with the addition of some printline debugging and `.unwrap()` calls:...