fix: hardcoded audio file extension failing validation in stt

[0xi4o]

No description provided.

[gemini-code-assist]

Summary of Changes

Hello @0xi4o, 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 resolves a critical bug in the audio processing pipeline where a hardcoded file extension was causing STT validation failures. By dynamically determining the file extension based on the MIME type, the system now supports a wider range of audio formats, improving the user experience and system reliability.

Highlights

• Audio File Extension Validation: The pull request addresses an issue where the hardcoded '.wav' extension for audio files was causing validation failures in speech-to-text (STT) processing.
• Dynamic Extension Handling: It introduces a function getRecordingExtensionForMime to dynamically determine the correct file extension based on the audio MIME type.
• MIME Type Mapping: The changes include a mapping of MIME types to corresponding file extensions, ensuring compatibility with various audio formats.

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

This pull request effectively resolves the issue of a hardcoded audio file extension by introducing a function to map MIME types to the correct extensions. This is a good fix. I've provided a couple of suggestions to further enhance the implementation for better performance and robustness.