Skip to content

Authenticate the Fluxions websocket - #458

Closed
coval-cale wants to merge 2 commits into
mainfrom
cale/bench-568-authenticate-the-fluxions-websocket
Closed

Authenticate the Fluxions websocket#458
coval-cale wants to merge 2 commits into
mainfrom
cale/bench-568-authenticate-the-fluxions-websocket

Conversation

@coval-cale

@coval-cale coval-cale commented Aug 6, 2026

Copy link
Copy Markdown
Contributor

Add auth to fluxions call so that we can use more credits

Greptile Summary

Adds authenticated Fluxions TTS websocket connections so benchmark runs can use account credits.

  • Adds FLUXIONS_API_KEY to environment-backed settings and the provider-key registry.
  • Requires the key when constructing the Fluxions provider and sends it as a bearer authorization header during the websocket handshake.
  • Updates Fluxions tests to cover the authorization header and missing-key behavior.

Confidence Score: 5/5

The PR appears safe to merge with Fluxions authentication consistently wired through configuration, provider construction, and websocket handshake tests.

The changed provider uses the repository's established secret configuration and websocket header conventions, while model eligibility prevents the absent arena deployment key from affecting current arena checks.

Reviews (1): Last reviewed commit: "Authenticate the Fluxions websocket" | Re-trigger Greptile

Context used:

Fluxions bot-gated the keyless VUI socket, so send the API key as a bearer header on the handshake and wire it through Settings, the provider key map, and tests.
@coval-cale
coval-cale requested a review from a team as a code owner August 6, 2026 15:39
@coderabbitai

coderabbitai Bot commented Aug 6, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@coval-cale, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 52 minutes

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 5cfab0a7-8091-4d6a-8b95-fa4deb38d83a

📥 Commits

Reviewing files that changed from the base of the PR and between 0799052 and e447911.

📒 Files selected for processing (6)
  • .env.example
  • runner/src/coval_bench/config.py
  • runner/src/coval_bench/providers/tts/fluxions.py
  • runner/src/coval_bench/registries/models.py
  • runner/src/coval_bench/registries/provider_keys.py
  • runner/tests/providers/tts/test_fluxions.py

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

…ticate-the-fluxions-websocket

# Conflicts:
#	.env.example
#	runner/src/coval_bench/config.py
#	runner/src/coval_bench/registries/provider_keys.py
@coval-cale coval-cale closed this Aug 6, 2026
@coval-cale
coval-cale deleted the cale/bench-568-authenticate-the-fluxions-websocket branch August 6, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant