Increase read_bufsize in minimax tts plugin

[jose-speak]

Summary by CodeRabbit

• Bug Fixes
  • Fixed a "Chunk too big" error that could occur when using minimax text-to-speech streaming by optimizing the internal buffer size for HTTP responses.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[CLAassistant]

All committers have signed the CLA.

[coderabbitai]

📝 Walkthrough

Walkthrough

A read_bufsize parameter with a 10 MB value is added to an HTTP POST request in the MiniMax TTS plugin. This parameter increases the buffer size used for streaming TTS responses to prevent a "Chunk too big" ValueError.

Changes

Cohort / File(s)	Summary
MiniMax TTS Buffer Optimization livekit-plugins/livekit-plugins-minimax/livekit/plugins/minimax/tts.py	Added read_bufsize=10*1024*1024 parameter to HTTP POST call for streaming TTS responses to increase buffer capacity and prevent chunk size errors

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A buffer so grand, ten megabytes wide,
No more "chunks too big" to cause our slide!
The streaming flows smooth, no errors in sight,
A tiny tweak here makes TTS just right! ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately and concisely describes the main change: increasing the read_bufsize parameter in the minimax TTS plugin to fix buffering issues.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

---

🧹 Recent nitpick comments

livekit-plugins/livekit-plugins-minimax/livekit/plugins/minimax/tts.py (1)

534-542: Consider centralizing the 10 MB buffer size as a constant/config.
This value may need future tuning; a module constant (or env/option) would make adjustments easier without touching logic.

♻️ Possible refactor

+READ_BUFSIZE_BYTES = 10 * 1024 * 1024  # 10 MB; avoids `ValueError: Chunk too big`
...
             async with self._tts._ensure_session().post(
                 url,
                 headers={
                     "Authorization": f"Bearer {self._opts.api_key}",
                 },
                 json=msg,
                 timeout=aiohttp.ClientTimeout(total=30, sock_connect=self._conn_options.timeout),
-                # large read_bufsize to avoid `ValueError: Chunk too big`
-                read_bufsize=10 * 1024 * 1024,
+                # large read_bufsize to avoid `ValueError: Chunk too big`
+                read_bufsize=READ_BUFSIZE_BYTES,
             ) as resp:

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between ffee15c and 6b71c2a.

📒 Files selected for processing (1)

• livekit-plugins/livekit-plugins-minimax/livekit/plugins/minimax/tts.py

🧰 Additional context used

📓 Path-based instructions (1)

**/*.py

📄 CodeRabbit inference engine (AGENTS.md)

**/*.py: Format code with ruff
Run ruff linter and auto-fix issues
Run mypy type checker in strict mode
Maintain line length of 100 characters maximum
Ensure Python 3.9+ compatibility
Use Google-style docstrings

Files:

• livekit-plugins/livekit-plugins-minimax/livekit/plugins/minimax/tts.py

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (2)

• GitHub Check: type-check (3.9)
• GitHub Check: unit-tests

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

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