v1.7.1:Improve error handling in Minio object retrieval methods

[asuiu]

Title

<type>: <short summary>

Ticket / Task

• [Trello|Jira] link: <URL>

What & Why

"Builds X so that Y can Z" – two sentences max.

Scope

• New feature
• Bug fix
• Refactor / tech-debt
• Test / tooling only

Checklist (self-review)

See Section 5.

Risk / Impact

• Latency critical path? ☐ Yes ☐ No
• External API contract change? ☐ Yes ☐ No
• Migration steps required? ☐ Yes ☐ No

Screenshots / Logs / Benchmarks

(only if relevant)

Author Self-Review Checklist

• Single Ticket — PR addresses only one business requirement / Trello card.
• Minimal Diff — no unrelated refactors, commented-out code, or debug prints.
• Compiles & Tests Pass — pytest -q / mvn test clean locally.
• No Dead Code — every new unit is called or covered by tests.
• Naming & Clarity — identifiers are self-explanatory; no overloaded meanings.
• Docs Updated — README, wiki, or docstrings updated where behaviour changed.
• Performance Tagged — if touching hot path, attach micro-benchmarks or profiler diff.
• Config & Secrets — no plaintext credentials; configs externalised.
• Rollback Ready — change can be reverted with git revert without dependency hell.
• Checklist Acknowledged — I would merge this myself if I were the reviewer.
• LLM Review — PR has been reviewed by the approved LLM tool and suggestions addressed.
  • IDE Type Checker — PyCharm/Pylance recommendations were addressed where applicable.
  • Optional mypy — (Recommended) Ran python/scripts/run_mypy.bat locally with no critical errors

Resources:

• PR guidelines

[coderabbitai]

Warning

Review limit reached

@asuiu, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 18 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f207b871-b2d3-47c2-bb7e-e3f0ddaa85c5

📥 Commits

Reviewing files that changed from the base of the PR and between 72587cf and e26d7dd.

⛔ Files ignored due to path filters (1)

• python/uv.lock is excluded by !**/*.lock

📒 Files selected for processing (7)

• python/bucketbase/ibucket.py
• python/bucketbase/minio_bucket.py
• python/bucketbase/versioned_minio_bucket.py
• python/pyproject.toml
• python/tests/config.py
• python/tests/test_minio_range_reader.py
• python/tests/test_versioned_minio_bucket.py

Warning

Billing warning: we have not been able to collect payment for this subscription for more than 72 hours. Please update the payment method or pay any pending invoices in Billing to avoid service interruption.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}