Skip to content

ci(strix): add same-provider NIM Nemotron fallbacks before GitHub Models - #733

Closed
seonghobae wants to merge 6 commits into
mainfrom
ci/strix-nim-fallback-chain
Closed

ci(strix): add same-provider NIM Nemotron fallbacks before GitHub Models#733
seonghobae wants to merge 6 commits into
mainfrom
ci/strix-nim-fallback-chain

Conversation

@seonghobae

@seonghobae seonghobae commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

Created accidentally during connector discovery. No project work is tracked here; the active source-repository ruleset incident remains #732.

seonghobae and others added 5 commits August 3, 2026 17:20
When the primary NVIDIA NIM model (nemotron-3-ultra-550b-a55b) is
rate-limited or unavailable, try nvidia_nim/nvidia/llama-3.1-nemotron-
ultra-253b-v1 and nvidia_nim/nvidia/nemotron-3-super-120b-a12b — both
already part of the contract-tested opencode NIM candidate pool — before
degrading to the cross-provider GitHub Models fallbacks (o3, gpt-5-chat).
NIM candidates reuse the already-provisioned NIM key and API base, and
the chain stays bounded by STRIX_TOTAL_TIMEOUT_SECONDS.

Updates the pinned contract assertion in test_strix_quick_gate.sh.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown

Warning

Review limit reached

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

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 938b1f20-0086-4c00-a568-343025bdb66a

📥 Commits

Reviewing files that changed from the base of the PR and between 3f65dbe and 133d791.

📒 Files selected for processing (5)
  • .github/workflows/strix.yml
  • scripts/ci/test_strix_quick_gate.sh
  • tests/conftest.py
  • tests/test_required_workflow_queue_contract.py
  • tests/test_strix_workflow_shell_contract.py

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

@seonghobae

Copy link
Copy Markdown
Contributor Author

@coderabbitai review

@coderabbitai

coderabbitai Bot commented Aug 4, 2026

Copy link
Copy Markdown
✅ Action performed

Review finished.

Note: CodeRabbit is an incremental review system and does not re-review already reviewed commits. This command is applicable only when automatic reviews are paused.

…navailable-fail-closed

chore: integrate fail-closed Strix wrapper with NIM fallbacks

Copy link
Copy Markdown
Contributor Author

Closing as superseded by #734. The same-provider NIM fallback chain is now present on #734 head 269456cfe749385f85e1928f3ebd30252d556504, combined with attempt-scoped crash-debris classification and a fail-closed wrapper that preserves provider exhaustion as incomplete security evidence.

@seonghobae seonghobae closed this Aug 4, 2026
auto-merge was automatically disabled August 4, 2026 09:28

Pull request was closed

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