Repository navigation
Conversation
Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
|
Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually. Contributors can view more details about this message here. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan provides up to 12 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe npm cache seed manifest now contains a new ChangesNPM cache seed
Priority: ⬇️ Low Estimated code review effort: 1 (Trivial) | ~2 minutes Merge Risk: ⚪ Minimal · up to The cache-seed manifest digest is updated to align with the current plugin lockfile, restoring integrity validation without changing archive inventory or runtime behavior. No current merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Code Coverage OverviewLanguages: TypeScript TypeScript / code-coverage/pluginThe overall line coverage in commit fbeef73 in the TypeScript / code-coverage/cliThe overall line coverage in commit fbeef73 in the Show a line coverage summary of the most impacted files.
Updated |
|
PR Review Advisor finished for commit |
|
Confirmed this current-main regression also blocks PR #11316 and unrelated PR #11319. On both, CLI shard 6 reaches the tests and fails the same integrity-pin assertion: manifest lockSha256 66bef669196bb1c61385871e369542d3c321c277adb0f0e2e9f0ad972106b163 versus current nemoclaw/package-lock.json SHA-256 55a512d782f8a4ad0eac39078b0e652400bf8580767b3a9ac5282a05bae47042. The focused one-line change here is the canonical fix. |
|
Maintainer CI classification for commit |
|
Closing as 3 PRs were opened to address this. Taking the one most mergable |
## Outcome Shared gateway startup and metadata-replacement messages now say “OpenShell gateway” without incorrectly identifying native Podman as Docker. Preflight continues to identify the selected runtime. ## Reason The reporter's [instrumented retest](#11311 (comment)) confirmed successful Podman startup and narrowed the issue to misleading legacy messages. The shared launcher retained Docker wording after it gained native Podman support. ### Related issues Fixes #11311 in its corrected messaging scope. ## Changes - Remove the Docker label from standalone startup, managed-service startup, and legacy metadata replacement. - Update gateway message assertions, the resume test's unwanted-startup check, and the Hermes startup-proof fixture. - Assert the managed-service startup message in the existing successful-start test. Strengthen the foreign-gateway and resume negative assertions, and check both startup messages as negative health fixtures in the mapped fast suite. Only three production strings change. No runtime selection, gateway lifecycle, or readiness behavior changes. ## Verification - `npx vitest run --project cli --project e2e-support src/lib/onboard/machine/handlers/gateway.test.ts src/lib/onboard/docker-driver-gateway-service.test.ts src/lib/onboard/docker-driver-gateway-env.test.ts src/lib/onboard/gateway/late-binding.test.ts test/e2e/support/hermes-gpu-startup-proof.test.ts` — 144 tests passed. - `npx vitest run --project cli --project integration src/lib/onboard/machine/handlers/gateway.test.ts test/runtime/gateway/gateway-state.test.ts` — 98 tests passed after the review repairs. - `npx tsx scripts/checks/e2e-mock-parity.mts --base origin/main --head HEAD` — passed. - `npm run validate:pr` — passed on the repaired commit. - The diff contains no secrets, API keys, or credentials. - No live E2E was dispatched manually: the changed contract is terminal wording. The existing live resume assertion was updated to retain its meaning. ## Review notes Self-review of NVIDIA/NemoClaw commit `5af927bb6f181b35687bd8ce4c4ba3d57ca00c69` covered the changed `src/lib/onboard/**` paths and both E2E test consumers. The three production changes are string replacements; control flow and security checks are unchanged. The diff removes three lines overall. CodeRabbit reviewed this commit with no actionable findings; both earlier review threads are resolved. The previous detection gap was that gateway tests did not check the managed-service message, while shared startup text still named Docker. This PR adds that assertion and updates the existing metadata and startup-proof coverage. It makes no broader Podman lifecycle qualification claim. Required CI run [34390148389](https://github.com/NVIDIA/NemoClaw/actions/runs/34390148389) passed 11 CLI shards and failed shard 6 on the inherited plugin cache-seed checksum mismatch. The fast/live parity failure is resolved. The checksum defect is identical on the recorded base and published branch; its canonical fix merged in #11314, superseding #11315. A local dependency refresh passes the 16 checksum/cache tests, but remains unpublished because the validation execution surface changed on canonical main `cad49353438e5ec6fd853eb51a1f6aded84090ff`. The published commit remains `5af927bb6f181b35687bd8ce4c4ba3d57ca00c69`; no CI waiver or broader Podman qualification is claimed. --- Signed-off-by: Aaron Erickson <aerickson@nvidia.com> <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **User Experience** * Updated gateway startup and upgrade messages to use consistent, generic OpenShell gateway terminology. * Improved lifecycle messaging when legacy gateway metadata is encountered. * **Bug Fixes** * Startup progress messages are no longer treated as an indication that the gateway is healthy. * **Tests** * Expanded coverage for gateway startup messaging, health status handling, resume output, and GPU startup scenarios. <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Signed-off-by: Aaron Erickson <aerickson@nvidia.com>
Outcome
The locked plugin cache-seed manifest matches
nemoclaw/package-lock.jsonagain. The OpenClaw integrity-pin contract and CLI shard 6 no longer reject currentmain.Reason
PR #10518 changed the plugin lockfile while leaving the generated cache-seed digest at the previous value. Current main CI therefore fails before unrelated PRs can reach a green gate.
Related issues
Refs #10518.
Blocks exact qualification of #11310.
Changes
Verification
shasum -a 256 nemoclaw/package-lock.json— produced55a512d782f8a4ad0eac39078b0e652400bf8580767b3a9ac5282a05bae47042.npx vitest run test/agents/openclaw/openclaw-integrity-pin-contract.test.ts test/install/materialize-locked-npm-cache-seed.test.ts— 16 tests passed.NODE_OPTIONS=--max-old-space-size=8192 npm run validate:pr— passed after building the current-main CLI and plugin artifacts required by a fresh checkout.Signed-off-by: Aaron Erickson aerickson@nvidia.com
Summary by CodeRabbit