Skip to content

fix(installer): preserve managed storage remediation - #8768

Merged
jyaunches merged 8 commits into
mainfrom
codex/installer-managed-storage-remediation
Aug 11, 2026
Merged

fix(installer): preserve managed storage remediation#8768
jyaunches merged 8 commits into
mainfrom
codex/installer-managed-storage-remediation

Conversation

@jyaunches

@jyaunches jyaunches commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Summary

Installer host preflight adopted canonical readiness admission in #8738 but hardcoded storage remediation off. Managed Docker overlayfs/containerd hosts therefore exited before onboarding could build the documented fuse-overlayfs replacement image. This change derives the waiver from canonical gateway lifecycle authority, keeps external, invalid, and non-remediable states blocked, and reports bounded admission IDs when preflight fails.

The first manual PR E2E run then exposed a separate parser mismatch after installer preflight: the generic GPU host reported valid NVIDIA driver 595.84, while the detector required exactly three numeric components. The bounded follow-up accepts two- or three-component NVIDIA versions without changing the minimum, resolver, schema, or supported surface.

Changes

  • Allow the installer storage exception only when the canonical gateway-management declaration is valid and absent or explicitly nemoclaw-managed; normal onboarding revalidates that authority before lifecycle effects.
  • Print deduplicated finding and capability IDs that satisfy the readiness schema's stable-ID grammar and length limit.
  • Cover absent and explicit managed authority, external supervision, invalid authority, non-remediable storage, onboarding continuation, and unsafe diagnostic input in installer integration tests.
  • Accept bounded two- or three-component NVIDIA driver versions while retaining numeric comparison, identical multi-GPU inventory, and fail-closed malformed-input behavior.

Type of Change

  • Code change (feature, bug fix, or refactor)
  • Code change with doc updates
  • Doc only (prose changes, no code sample modifications)
  • Doc only (includes code sample changes)

Quality Gates

  • Tests added or updated for changed behavior
  • Existing tests cover changed behavior — justification:
  • Tests not applicable — justification:
  • Docs updated for user-facing behavior changes
  • Docs not applicable — justification: this restores the documented managed-only storage remediation path and accepts a valid NVIDIA driver form above the existing documented 580.65.06 minimum. It adds no command, configuration, schema, minimum, or support claim.
  • Sensitive paths changed (security, policy, credentials, preflight, onboarding, inference, runner, sandbox, or messaging)
  • Sensitive-path review completed or maintainer-approved waiver recorded — reviewer/approval link/justification: an independent Codex Desktop review of exact head 4d78d7355 on base acda7aa22 passed all nine security categories with no findings. It verified canonical authority parsing and revalidation, managed-only lifecycle effects, fail-closed external/invalid/non-remediable states, sanitized admission IDs, and strict bounded driver parsing.
  • Non-success, skipped, or missing CI check accepted by maintainer — check name, approval link, and follow-up issue:

Documentation Writer Review

  • Documentation writer subagent reviewed the completed changes
  • Result: no-docs-needed
  • Evidence: docs/get-started/prerequisites.mdx, docs/reference/system-readiness.mdx, and docs/deployment/gateway-lifecycle-authority.mdx already document managed storage remediation and external lifecycle authority. docs/inference/set-up-llama-cpp.mdx already requires NVIDIA driver version 580.65.06 or later; accepting valid two- or three-component versions restores that contract. The generic Linux preset remains explicit-only and experimental.
  • Agent: Codex Desktop

DGX Station Hardware Evidence

  • Tested on DGX Station
  • Tested commit:
  • Station profile/scenario:
  • Result:
  • Supporting evidence:

Verification

  • PR description includes a Signed-off-by: line and every commit appears as Verified in GitHub
  • Normal pre-commit, commit-msg, and pre-push hooks passed, or npm run validate:pr passed after refreshing origin/main when hooks were skipped or unavailable
  • Targeted behavior tests pass for the current change set, or tests are marked not applicable above — command/result:
    • npm exec -- vitest run --project installer-integration test/install-preflight.test.ts --maxWorkers=4 — exact reviewed patch passed 98/99; the unrelated five-second release-tag fixture timed out, then passed alone 1/1. The six changed readiness cases passed, and the byte-identical pre-merge candidate passed 99/99 under the same worker limit.
    • npm exec -- vitest run --project cli src/lib/inference/nim-driver-version.test.ts src/lib/inference/llama-cpp/managed-selection.test.ts src/lib/inference/serving/resolver.test.ts — 49/49 passed.
    • npm exec -- vitest run --project e2e-support test/e2e/support/base-image-publication.test.ts — 39/39 passed after merging upstream repairs fix(ci): complete main-only lifecycle evidence #8771 and test(ci): require lifecycle publisher paths #8772.
    • npm run test:changed — passed; the clean checkout selected no CLI, plugin, or E2E-support source tests and the integrated growth contract passed 4/4.
    • npm run validate:pr — passed all pre-commit, commit-message, and pre-push checks at exact head.
    • The requested npm exec -- vitest run --project integration test/install-preflight.test.ts reports no matching tests because project membership assigns this file to installer-integration; the owning lane is recorded above.
    • Ordinary manual PR E2E run 31444706504 passed six of the seven installer-path jobs at the prior head. llama-cpp-generic-gpu passed installer preflight and exposed the two-component driver parser mismatch fixed here. Exact-head E2E is pending.
  • Applicable broad gate passed — npm test for broad runtime/test-harness changes; npm run check for repo-wide validation/coverage changes — command/result: not applicable to these bounded installer-admission and driver-parser changes; targeted installer and CLI suites plus required CI are the applicable evidence.
  • Quality Gates section completed with required justifications or waivers
  • No secrets, API keys, or credentials committed
  • npm run docs builds without warnings (doc changes only)
  • Doc pages follow the style guide (doc changes only)
  • New doc pages include SPDX header and frontmatter (new pages only)

Signed-off-by: Julie Yaunches jyaunches@nvidia.com

Summary by CodeRabbit

  • Bug Fixes
    • Installer preflight now limits storage remediation to supported, explicitly managed gateway configurations.
    • Host-admission failures provide validated, deduplicated finding and capability identifiers alongside existing diagnostics.
    • Installer onboarding behavior and failure reporting are now more consistent across gateway lifecycle states.
    • NVIDIA driver detection more reliably handles repeated version output and rejects malformed or contaminated results.

Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
@jyaunches jyaunches self-assigned this Aug 10, 2026
@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: eae622c0-2c26-4322-bd22-b4818487bee5

📥 Commits

Reviewing files that changed from the base of the PR and between 6a2c2ad and 26d529d.

📒 Files selected for processing (2)
  • scripts/install.sh
  • src/lib/inference/nim-driver-version.test.ts
🚧 Files skipped from review as they are similar to previous changes (2)
  • src/lib/inference/nim-driver-version.test.ts
  • scripts/install.sh

📝 Walkthrough

Walkthrough

The installer host preflight now gates storage remediation by gateway-management state and sanitizes admission identifiers. Shared test helpers cover these cases. NVIDIA driver-version tests now cover uniform and invalid command output.

Changes

Storage remediation admission

Layer / File(s) Summary
Installer preflight admission flow
scripts/install.sh
The preflight loads gateway-management support, permits storage remediation only for undeclared or NemoClaw-managed gateways, and emits validated, deduplicated finding and capability IDs.
Admission test harness and coverage
test/helpers/installer-readiness-stubs.ts, test/install-preflight.test.ts
Shared helpers simulate gateway states, remediation availability, onboarding, and diagnostic sanitization. Tests cover admission outcomes and onboarding behavior.

NVIDIA driver version validation

Layer / File(s) Summary
Driver inventory validation coverage
src/lib/inference/nim-driver-version.test.ts, src/lib/inference/serving/resolver.test.ts
Tests cover duplicate uniform versions, malformed and mixed inventories, ANSI output, command options, and a nonmatching version comparison.

Estimated code review effort: 3 (Moderate) | ~20 minutes

Sequence Diagram(s)

sequenceDiagram
  participant Installer as run_installer_host_preflight
  participant Gateway as gateway-management module
  participant Admission as readiness admission evaluator
  participant Onboarding as onboard session
  Installer->>Gateway: load gateway declaration
  Gateway-->>Installer: return gateway mode
  Installer->>Admission: evaluate storage remediation permission
  Admission-->>Installer: return admission result and IDs
  Installer->>Onboarding: run onboarding when admission passes
Loading

Possibly related PRs

  • NVIDIA/NemoClaw#8738: Both changes update installer host-readiness admission in scripts/install.sh.
  • NVIDIA/NemoClaw#8748: Both changes modify storage-remediation admission and installer preflight coverage.

Suggested labels: area: install, area: onboarding, bug-fix, platform: container

Suggested reviewers: cv

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main installer change: preserving storage remediation for managed environments.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch codex/installer-managed-storage-remediation

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

@github-code-quality

github-code-quality Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

Code Coverage Overview

Languages: TypeScript

TypeScript / code-coverage/plugin

The overall coverage in commit 4d78d73 in the codex/installer-mana... branch remains at 96%, unchanged from commit acda7aa in the main branch.


Updated August 11, 2026 02:10 UTC

@github-actions

github-actions Bot commented Aug 10, 2026

Copy link
Copy Markdown
Contributor

PR Review Advisor — No blocking findings reported

Advisor assessment: No blocking advisor findings reported
Next action: No advisor follow-up needed.
Findings: 0 blockers · 0 warnings · 0 suggestions

Model lanes

  • GPT-5.6 Terra (primary): Completed · medium confidence · 0 blockers · 0 warnings · 0 suggestions
  • Nemotron 3 Ultra (second opinion): Failed

Second-opinion terminology and E2E selections are advisory. Live E2E does not run automatically for pull requests.

3 semantic terminology decisions

Terminology decisions are advisory. They affect the assessment only when a separate finding identifies concrete semantic impact.

  • established — gateway lifecycle authority at test/install-preflight.test.ts:1144: Retain gateway lifecycle authority. The controlled word list and existing repository sources use this term consistently.
  • justified — admission finding IDs at scripts/install.sh:3104: Retain admission finding IDs. The modifier identifies the bounded readiness-admission output contract.
  • justified — NVIDIA driver inventory at src/lib/inference/nim-driver-version.test.ts:12: Retain NVIDIA driver inventory. The modifier identifies the multi-row parser input that the test verifies.

E2E guidance

Advisory only. A maintainer can dispatch the default E2E suite against this exact revision.

Recommended E2E: cloud-onboard, managed-image-multiarch-startup, inference-routing, network-policy

2 optional E2E recommendations
  • llama-cpp-generic-gpu
  • vllm-docker-storage

Workflow run details

This automated review informs maintainers. Warnings and suggestions do not require a response. A maintainer decides whether to merge.

Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
jyaunches added a commit that referenced this pull request Aug 11, 2026
<!-- markdownlint-disable MD041 -->
## Summary

This PR updates the August 10, 2026 v0.0.106 release entry with gateway
readiness fixes that merged after PR #8756.
PRs #8765, #8767, and #8768 remain outside this entry because they are
open and do not carry the `v0.0.106` release label.

## Changes

- Document acceptance of OpenShell v0.0.101 `Server:` endpoint output
and target-bound process tags when trusted listener evidence matches the
configured gateway.
- Document preservation of selected-gateway stale state so onboarding
can reconcile a registered gateway when a gateway-scoped OpenShell
status check cannot connect.
- Record evidence-backed exclusions for internal image, startup,
qualification, proxy-environment, CI, and test-harness changes in PRs
#8754, #8609, #8762, #8432, #8766, and #8581.
- Exclude PRs #8765, #8767, and #8768 because their changes are absent
from `main` and the PRs do not carry the `v0.0.106` release label.
The release entry must be updated after any of those PRs merges for
v0.0.106.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [ ] Code change with doc updates
- [x] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates

- [ ] Tests added or updated for changed behavior
- [x] Existing tests cover changed behavior — justification:
`test/changelog-docs.test.ts` validates dated changelog SPDX placement,
version headings, forbidden terms, and link form.
- [ ] Tests not applicable — justification:
- [x] Docs updated for user-facing behavior changes
- [ ] Docs not applicable — justification:
- [ ] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [ ] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification:
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Documentation Writer Review

- [x] Documentation writer subagent reviewed the completed changes
- Result: `docs-updated`
- Evidence: `docs/changelog/2026-08-10.mdx`; an independent Codex
Desktop subagent reviewed the writing rules and documentation style,
terminology, structure, voice, code-sample presentation, links, source
and test accuracy, release meaning, product scope, and evidence-backed
exclusions at commit `190bf882c`.
- Agent: Codex Desktop
<!-- docs-review-head-sha: 190bf88 -->
<!-- docs-review-agents-blob-sha: c4923a3 -->

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable; `scripts/prepare-dgx-station-host.sh`
is unchanged.
- Station profile/scenario: Not applicable.
- Result: Not applicable.
- Supporting evidence: Not applicable.

## Verification

- [x] PR description includes a `Signed-off-by:` line and every commit
appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run validate:pr` passed after refreshing `origin/main` when hooks
were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — command/result or justification: `npx
vitest run test/changelog-docs.test.ts` passed 6 tests.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: Not applicable to a
documentation-only release-entry update.
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) —
result: passed with 0 errors and 2 existing warnings.
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)
— no page was added.

---
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

* **Bug Fixes**
* Improved gateway readiness detection for OpenShell v0.0.101 endpoint
output.
* Process tags are now accepted only when they match trusted listener
information for the configured gateway.
* Preserved stale gateway status during connection failures to support
accurate onboarding reconciliation.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Carlos Villela <cvillela@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick comments (1)
src/lib/inference/nim.ts (1)

708-708: 🗄️ Data Integrity & Integration | 🔵 Trivial | ⚡ Quick win

Add a two-component driver-version boundary test.

version-at-least accepts 595.84 and compares missing components as zero. Existing tests do not pass a two-component value through both createHostReadinessReport and resolveManagedInferenceServing; add this public-boundary coverage.

🤖 Prompt for 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.

In `@src/lib/inference/nim.ts` at line 708, Add public-boundary tests using a
two-component driver version such as 595.84, passing it through both
createHostReadinessReport and resolveManagedInferenceServing. Verify
version-at-least accepts the value and compares its missing component as zero,
while preserving existing behavior for other version formats.

Source: Path instructions

🤖 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.

Nitpick comments:
In `@src/lib/inference/nim.ts`:
- Line 708: Add public-boundary tests using a two-component driver version such
as 595.84, passing it through both createHostReadinessReport and
resolveManagedInferenceServing. Verify version-at-least accepts the value and
compares its missing component as zero, while preserving existing behavior for
other version formats.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: d8bdbe40-ac67-4408-9f2c-f8fe6e55d21f

📥 Commits

Reviewing files that changed from the base of the PR and between e9fa41b and 6a2c2ad.

📒 Files selected for processing (4)
  • src/lib/inference/llama-cpp/managed-selection.test.ts
  • src/lib/inference/nim-driver-version.test.ts
  • src/lib/inference/nim.ts
  • src/lib/inference/serving/resolver.test.ts

jyaunches and others added 3 commits August 10, 2026 21:45
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
Signed-off-by: Julie Yaunches <jyaunches@nvidia.com>
@copy-pr-bot

copy-pr-bot Bot commented Aug 11, 2026

Copy link
Copy Markdown

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@jyaunches
jyaunches merged commit cb7f2bd into main Aug 11, 2026
23 checks passed
@jyaunches
jyaunches deleted the codex/installer-managed-storage-remediation branch August 11, 2026 02:31
prekshivyas pushed a commit that referenced this pull request Aug 11, 2026
<!-- markdownlint-disable MD041 -->
## Summary
Completes the v0.0.106 changelog for four user-visible changes that
merged before the tag but were omitted from the pre-tag entry. Keeps
public security pages focused on operator guidance by relocating
maintenance contracts to contributor guidance and the owning OpenClaw
dependency review. Records PR #8753's portable inference descriptor as
Experimental while leaving its existing workflow documentation
unchanged.

## Changes

- Add managed-container restart-transition recovery from PR #8765,
Shields parent-owner preservation from PR #8767, and managed storage
remediation plus NVIDIA driver parsing from PR #8768 to the canonical
v0.0.106 entry.
- Add the Experimental portable inference descriptor from PR #8753 to
the v0.0.106 entry, including its short-lived credential boundary,
manual standby behavior, and owning setup page.
- Keep Process Controls focused on the operator-facing immutable-image
boundary and move the blueprint image-pin maintenance contract to
`CONTRIBUTING.md`.
- Keep Gateway and Secret Controls focused on operator actions and move
the OpenClaw audit-suppression tests and distinct removal conditions to
the owning OpenClaw 2026.7.1 dependency review.

## Type of Change

- [ ] Code change (feature, bug fix, or refactor)
- [ ] Code change with doc updates
- [x] Doc only (prose changes, no code sample modifications)
- [ ] Doc only (includes code sample changes)

## Quality Gates

- [ ] Tests added or updated for changed behavior
- [x] Existing tests cover changed behavior — justification: the
dated-changelog, published-route, and documentation-link tests cover the
changed release entry and links.
- [ ] Tests not applicable — justification:
- [x] Docs updated for user-facing behavior changes
- [ ] Docs not applicable — justification:
- [x] Sensitive paths changed (security, policy, credentials, preflight,
onboarding, inference, runner, sandbox, or messaging)
- [x] Sensitive-path review completed or maintainer-approved waiver
recorded — reviewer/approval link/justification: an independent Codex
Desktop documentation writer reviewed exact head `bbfed36ca`; the review
verified the operator-facing security claims, the distinct
`allowInsecureAuth` and device-auth suppression removal conditions
against their generator branches, and the confirmed Experimental #8753
release claim. No runtime or policy behavior changes.
- [ ] Non-success, skipped, or missing CI check accepted by maintainer —
check name, approval link, and follow-up issue:

## Documentation Writer Review

- [x] Documentation writer subagent reviewed the completed changes
- Result: `docs-updated`
- Evidence: `CONTRIBUTING.md`, `docs/changelog/2026-08-10.mdx`,
`docs/security/gateway-authentication-controls.mdx`,
`docs/security/openclaw-2026.7.1-dependency-review.md`, and
`docs/security/process-controls.mdx`; the subagent reviewed
`docs/CONTRIBUTING.md`, `WRITING.md`, terminology, structure, voice,
code-sample presentation, canonical ownership, factual accuracy, and
product scope.
- Agent: Codex Desktop
<!-- docs-review-head-sha: bbfed36 -->
<!-- docs-review-agents-blob-sha: c4923a3 -->

## DGX Station Hardware Evidence

- [ ] Tested on DGX Station
- Tested commit: Not applicable; `scripts/prepare-dgx-station-host.sh`
is unchanged.
- Station profile/scenario: Not applicable.
- Result: Not applicable.
- Supporting evidence: Not applicable.

## Verification

- [x] PR description includes a `Signed-off-by:` line and every commit
appears as `Verified` in GitHub
- [x] Normal `pre-commit`, `commit-msg`, and `pre-push` hooks passed, or
`npm run validate:pr` passed after refreshing `origin/main` when hooks
were skipped or unavailable
- [x] Targeted behavior tests pass for the current change set, or tests
are marked not applicable above — command/result or justification: `npx
vitest run test/changelog-docs.test.ts
test/check-docs-published-routes.test.ts test/check-docs-links.test.ts`
passed; `npm run docs` and `git diff --check` passed again after the
review correction.
- [ ] Applicable broad gate passed — `npm test` for broad
runtime/test-harness changes; `npm run check` for repo-wide
validation/coverage changes — command/result: not applicable to this
bounded documentation-only change.
- [x] Quality Gates section completed with required justifications or
waivers
- [x] No secrets, API keys, or credentials committed
- [ ] `npm run docs` builds without warnings (doc changes only) —
result: passed with zero errors and the existing light-mode accent
contrast warning.
- [x] Doc pages follow the [style
guide](https://github.com/NVIDIA/NemoClaw/blob/main/docs/CONTRIBUTING.md)
(doc changes only)
- [ ] New doc pages include SPDX header and frontmatter (new pages only)
— no new pages.

---
Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>


<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->

## Summary by CodeRabbit

- **Documentation**
- Documented requirements for keeping managed sandbox image digest pins
synchronized and immutable.
- Added guidance for validating custom images and using reviewed image
sources during onboarding.
- Expanded release notes with portable inference profiles, endpoint
references, cleanup behavior, startup handling, and installer details.
- Updated security documentation with current dependency-review
information and authentication-control boundaries.
- Clarified sandbox ownership, permissions, workload identity, and
managed-container restart behavior.

<!-- end of auto-generated comment: release notes by coderabbit.ai -->

---------

Signed-off-by: Miyoung Choi <miyoungc@nvidia.com>
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.

2 participants