Repository navigation
Conversation
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughHosted inference staging now rewrites compatible environment values and readiness checks use a reachability probe. Deep Agents startup now conditionally ensures ChangesHosted inference routing and probes
Deep Agents startup check
Session JSON parsing
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes Possibly related PRs
Suggested labels
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall coverage in the Show a code coverage summary of the most covered files.
TypeScript / code-coverage/cliThe overall coverage in the Show a code coverage summary of the most covered files.
Updated |
PR Review Advisor — Changes requestedMerge posture: Do not merge yet Action checklist
Findings index
Review findings by urgency: 0 required fixes, 8 items to resolve/justify, 0 in-scope improvements
|
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/lib/onboard/providers.ts`:
- Around line 260-271: The build-selection staging path in providers.ts is
overriding an explicit COMPATIBLE_API_KEY with sourceKey because
hostedCompatibleBuildSelection now routes into the same write branch as implicit
cases. Update the staging logic around shouldStage and the subsequent write
branch in the provider-selection flow so that when compatibleKey is already
present, the code preserves that explicit credential instead of assigning
sourceKey; keep the existing precedence behavior tied to compatibleKey and only
populate sourceKey for implicit or non-compatible cases.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Enterprise
Run ID: 9030e8ed-f7b3-47e8-b49e-13f24a04bd1d
📒 Files selected for processing (11)
src/lib/onboard/providers.test.tssrc/lib/onboard/providers.tstest/deepagents-code-tui-startup-check.test.tstest/e2e-scenario/fixtures/redaction.tstest/e2e-scenario/live/hermes-e2e.test.tstest/e2e-scenario/live/model-router-provider-routed-inference.test.tstest/e2e-scenario/live/sandbox-survival.test.tstest/e2e-scenario/live/sessions-agents-cli.test.tstest/e2e-scenario/support-tests/hosted-inference.test.tstest/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.shtest/e2e/test-sessions-agents-cli.sh
E2E Advisor RecommendationRequired E2E: None Full advisor summaryE2E Recommendation AdvisorBase: Required E2E
Optional E2E
New E2E recommendations
|
Vitest E2E Scenario RecommendationRequired Vitest E2E scenarios: Dispatch required Vitest E2E scenarios:
Full Vitest E2E advisor summaryVitest E2E Scenario AdvisorBase: Required Vitest E2E scenarios
Optional Vitest E2E scenarios
Relevant changed files
|
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
PR Review Advisor (Nemotron Ultra) — InformationalMerge posture: Informational / low confidence Action checklist
Findings index
Review findings by urgency: 0 required fixes, 1 item to resolve/justify, 0 in-scope improvements
|
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Carlos Villela <cvillela@nvidia.com>
|
Superseded by #5887 because force-push is disabled on PR branches and the replacement branch has a clean conventional commit history. |
Summary
Fixes the first release-gate E2E failures found while running the v0.0.69 full nightly candidate: hosted-compatible CI onboarding now overrides explicit cloud selection, Deep Agents TUI checks skip non-Deep-Agents sandboxes before requiring
expect, and JSON/live reachability probes tolerate CI warning and endpoint behavior.Changes
NEMOCLAW_E2E_USE_HOSTED_INFERENCE=1+NEMOCLAW_PROVIDER=cloudthrough the compatible endpoint while keeping normal explicit cloud behavior unchanged.expect./v1/modelspreflights in live Vitest Hermes/sandbox-survival scenarios.nvapi-*key.Type of Change
Quality Gates
NEMOCLAW_E2E_USE_HOSTED_INFERENCErouting and fixture secret filtering; source credentials remain excluded from default child env.Verification
Verifiedin GitHubnpx prek run --from-ref main --to-ref HEADpassesnpm testpasses (broad runtime changes only)npm run docsbuilds without warnings (doc changes only)Targeted verification run:
npm run build:cli npm test -- --run src/lib/onboard/providers.test.ts test/deepagents-code-tui-startup-check.test.ts test/e2e-scenario/support-tests/hosted-inference.test.ts bash -n test/e2e/e2e-cloud-experimental/checks/10-deepagents-code-tui-startup.sh test/e2e/test-sessions-agents-cli.sh npm run typecheck:cliLocal hooks were attempted but the broad local test hook failed on unrelated environment-sensitive tests (Hermes tempdir mode and sandbox rlimit hook); the focused checks above cover this diff.
Signed-off-by: Carlos Villela cvillela@nvidia.com
Summary by CodeRabbit
expectis available when possible.