Repository navigation
fix(onboard): reduce dashboard forward authority checks - #12484
Conversation
Signed-off-by: Rebecca Sliter <571084+rsliter@users.noreply.github.com>
|
Navigate logical layers of code changes, visualize relationships, and explore their blast radius. No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository: NVIDIA/NemoClaw/.coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review. 📝 WalkthroughWalkthroughThe dashboard forward observer now checks authority once after it receives and validates the adapter’s observations. The tests cover stale authority before and during collection, fresh checks on subsequent batches, and mismatched-identity responses. ChangesDashboard forward authority check
Priority: ➖ Normal Estimated code review effort: 2 (Simple) | ~10 minutes Change: Bug fix · Severity of issue fixed: Medium Suggested reviewers: Merge Risk: ⚪ Minimal · up to The change reduces repeated authority checks during dashboard forward observation, which addresses the reported onboarding timeout on macOS. No merge-blocking risk was found. WSL and cloud cases still need live retesting, as the author notes. 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches 💡 1📝 Generate docstrings 💡
🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit 1627a32 in the Show a line coverage summary of the most impacted files.
TypeScript / code-coverage/cliThe overall line coverage in commit 1627a32 in the Show a line coverage summary of the most impacted files.
Updated |
Outcome
Dashboard forward observation now performs one gateway authority check for each valid read-only multi-port batch instead of repeating synchronous ownership checks for every unbound port. The final fence rejects the complete batch if gateway authority is stale or changes during observation.
Reason
On macOS with a Homebrew-managed gateway, the 11-port dashboard scan performed 27 synchronous formula identity operations and consumed about 32.6 seconds, exceeding the 15-second observation budget.
Related issues
Refs #11963
Changes
Verification
NODE_OPTIONS=--max-old-space-size=8192 npm run validate:prpassed repository checks, secret scanning, CLI and plugin builds, publication validation, and CLI TypeScript checks.npx vitest run --project cli src/lib/onboard/dashboard-port.test.ts src/lib/adapters/openshell/forward-cli.test.tspassed 123 tests in 2 files.npx vitest run --project integration test/automation/pull-requests/growth-guardrails.test.tspassed 7 tests.Review notes
1627a326478679c0c195c8b203e219c406a69aa4changessrc/lib/onboard/dashboard-port.tsand its focused test. The coordinating agent independently reviewed the measured root cause, sibling forward-allocation paths, and wrapper-only final-fence design before commit. The exact final candidate also received local self-review. Automated and independent human review remain pending.Signed-off-by: Rebecca Sliter 571084+rsliter@users.noreply.github.com
Summary by CodeRabbit