Sebastian Thiel

Thanks for bringing this up. Let me take it upon myself to close it, as I think it has been superseded by now.

Maybe it's out-of-date. I think you can regenerate locally after trying `make update-json` to get the latest versions of all API declarations.

As an update, sparse-indices are supported in the sense that they can be read, and every index interaction does consider them. It's a bit of a fringe feature right now...

Can it be clarified how this issue relates to #4852? It seems like the PR is lacking the dedicated backend function, but probably I am missing some details.

Indeed, there really is 'just' [this PR](https://github.com/Byron/gitoxide/pull/1368) missing which I plan to work on for months now. It will happen though…I am just spread thin ATM.

Please note that I have been using these PRs for other things and keep reopening them, so the mere merge doesn't really say much about its contents. Thus, `is_dirty` isn't...

It seems that updating the workspace is indeed a way to produce this issue, see [this discord message](https://discord.com/channels/1060193121130000425/1073202153163857920/1368727328124833882).

Thanks for chiming in! For context, we will be rewriting the update-workspace functionality which should shake things up a little, but the question remains if the Rust code is meaningfully...

That sounds good, thanks again for your help! > 3\. Harden reads there by replacing any brittle `read_exact` with a buffered loop/`io::copy` and surface richer error context for `UnexpectedEof` (read/expected...

Thanks a lot for reporting! It's sad to see the issue is so spurious. From a quick attempt I can say that it doesn't obviously reproduce - files dragged over...