Simplify stripe_fetcher

[pykello]

Summary

• remove unused stripes_fetched field from StripeFetcher

Testing

• cargo fmt --all -- --check
• cargo clippy --all-targets --all-features -- -D warnings
• cargo test
• cargo test --features disable-isal-crypto

---

https://chatgpt.com/codex/tasks/task_e_6889d3d9475883279df07688f411cd5e

[Copilot]

Pull Request Overview

This PR simplifies the StripeFetcher by removing the unused stripes_fetched field that was tracking the number of successfully fetched stripes.

• Removes the stripes_fetched field from the StripeFetcher struct
• Removes the initialization and increment logic associated with this field
• Maintains existing functionality while reducing code complexity

[greptile-apps]

Greptile Summary

This PR removes the unused stripes_fetched field from the StripeFetcher struct in the stripe fetcher module. The StripeFetcher is a core component of the lazy block device implementation that manages fetching data stripes from a source device to a target device in a concurrent manner.

The removed field was a simple usize counter that tracked the number of successfully fetched stripes. While it was properly maintained (initialized to 0 in the constructor and incremented in the fetch_completed method when a stripe fetch succeeded), it was never actually read or used by any logic in the system. The actual stripe status tracking is already handled comprehensively by the stripe_status_vec field, which maintains detailed status information for each individual stripe using atomic operations for thread safety.

This change fits well with the codebase's design as it removes redundant tracking without affecting the core functionality. The StripeFetcher continues to manage concurrent fetch operations, handle fetch queues, and update stripe statuses through its existing mechanisms. The removal simplifies the struct's interface and reduces unnecessary maintenance overhead.

Confidence score: 5/5

• This PR is extremely safe to merge as it only removes unused dead code without affecting any functionality.
• The field was never read anywhere in the codebase, making its removal completely risk-free.
• No files need additional attention - this is a straightforward cleanup.

_{1 file reviewed, no comments}

_{Edit Code Review Bot Settings | Greptile}