Authenticate the Fluxions websocket - #458
Conversation
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.
|
Warning Review limit reached
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 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 configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (6)
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. Comment |
…ticate-the-fluxions-websocket # Conflicts: # .env.example # runner/src/coval_bench/config.py # runner/src/coval_bench/registries/provider_keys.py
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.
FLUXIONS_API_KEYto environment-backed settings and the provider-key registry.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: