fix: preserve exception chain

[b-long]

Consistently link new exceptions to their original causes

[gemini-code-assist]

Summary of Changes

Hello @b-long, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request enhances the robustness and diagnostic capabilities of the application's error handling. By consistently linking new exceptions to their original causes, it provides a clearer picture of failure points, which is crucial for maintenance and troubleshooting. The changes span various modules, ensuring that error propagation retains full context. Additionally, a minor adjustment to the linting configuration will help catch more potential issues during development.

Highlights

• Improved Exception Chaining: The primary change across the codebase is the adoption of explicit exception chaining using raise ... from e in Python. This ensures that the original cause of an exception is preserved when a new exception is raised, significantly improving debuggability and error context.
• Linting Configuration Update: The pyproject.toml file has been updated to broaden the flake8-bugbear checks from B0 to B, enabling more comprehensive linting for potential bugbear issues.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

The pull request correctly preserves exception chains by using raise ... from ..., which is a great improvement for debuggability. The configuration change in pyproject.toml to enable more flake8-bugbear checks is also a positive step towards better code quality. My review includes a few suggestions to further improve exception handling by making exception messages more informative and removing some redundancy in how exceptions are constructed.