forge fix: replace panic-prone .unwrap() calls with proper error handling i…

…n router

Replace JSON deserialization unwrap with match expression and fallback to original patch on error
Replace MIME parsing unwrap with unwrap_or_else and fallback to application/octet-stream
Add tracing logs for error cases to aid debugging

This prevents production crashes on edge cases while maintaining graceful degradation.

Nov 27 '25 17:11 jmanhype

Summary of Changes

Hello @jmanhype, I'm Gemini Code Assist[^1]! 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 significantly enhances the application's resilience by replacing several unwrap() calls in the router with robust error handling mechanisms. These changes prevent potential crashes due to malformed input or unexpected data, ensuring that the application can gracefully degrade and continue operating even when encountering edge cases. The introduction of detailed logging for these error paths also improves observability and simplifies future debugging efforts.

Highlights

Robust Error Handling for JSON Deserialization: Replaced a panic-prone .unwrap() call during JSON patch deserialization with a match expression, allowing for graceful error handling and fallback to the original patch value if deserialization fails.
Improved MIME Type Parsing: Switched from .unwrap() to .unwrap_or_else() for MIME type header value creation, ensuring that invalid MIME types are handled by falling back to application/octet-stream instead of crashing.
Enhanced Debugging with Tracing Logs: Added tracing::error! and tracing::warn! logs for error and fallback scenarios, providing better visibility and aiding in debugging potential issues in production.

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 :thumbsup: and :thumbsdown: 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.

[^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.