Fix chunking fallback#10
Conversation
Summary of ChangesHello @cotid-qualabs, I'm Gemini Code Assist1! 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 refines the logic for low-latency streaming by ensuring that chunked segment writing is only activated when an explicit chunk duration is provided. This change prevents unintended fallback to chunked mode with derived durations and instead defaults to standard live segment writing, making the system's behavior more predictable and robust. It also introduces an error state for cases where chunking is implicitly requested without the necessary configuration. Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request correctly addresses an issue where chunked transfer was the default behavior for low-latency streams. The changes ensure that chunking is now an opt-in feature, activated only when a chunk duration is explicitly specified through the chunkDurS or chunkDurSSR parameters. The fallback mechanism has been corrected to serve a complete segment, which is the appropriate default. Additionally, the error handling within prepareChunks has been improved for clarity, and the tests have been updated to reflect these new requirements. The implementation is clean and effectively resolves the problem.
Addressing comment #9 (comment)