Skip to content

fix: make onboard robust when rerun after a failed install#84

Closed
WuKongAI-CMU wants to merge 1 commit intoNVIDIA:mainfrom
WuKongAI-CMU:fix/onboard-rerun-robustness
Closed

fix: make onboard robust when rerun after a failed install#84
WuKongAI-CMU wants to merge 1 commit intoNVIDIA:mainfrom
WuKongAI-CMU:fix/onboard-rerun-robustness

Conversation

@WuKongAI-CMU
Copy link
Copy Markdown
Contributor

Summary

Fixes #23nemoclaw onboard now handles reruns gracefully without requiring uninstall.sh.

Root cause: After a failed onboard, the sandbox could exist in OpenShell but not in the local registry (or vice versa). The code only checked the registry, so it either tried to create a duplicate or missed the orphan entirely.

Fix: createSandbox() now checks both the registry and OpenShell:

  • Shows which side has the sandbox (e.g. "found in OpenShell but not registered")
  • Keeping an orphan sandbox re-syncs the registry automatically
  • Recreating cleans up both sides before proceeding

Test plan

  • Existing tests pass (19/19)
  • Manual: run nemoclaw onboard, kill during sandbox creation, rerun → should detect orphan and offer to recreate or keep
  • Manual: run nemoclaw onboard after successful install → should detect existing sandbox and offer to reconfigure

🤖 Generated with Claude Code

When a previous onboard attempt failed partway through, the sandbox
could exist in OpenShell but not in the local registry (or vice
versa). Rerunning onboard would then either try to create a duplicate
sandbox (failing) or miss the existing one entirely, requiring
`uninstall.sh` as a workaround.

Now `createSandbox()` checks both the local registry and the actual
OpenShell state. When they are out of sync:
- The user sees which side has the sandbox (e.g. "found in OpenShell
  but not registered")
- Choosing to keep it re-syncs the registry automatically
- Choosing to recreate cleans up both sides before proceeding

Closes NVIDIA#23

Signed-off-by: peteryuqin <peter.yuqin@gmail.com>
@wscurran wscurran added bug Something isn't working NemoClaw CLI Use this label to identify issues with the NemoClaw command-line interface (CLI). labels Mar 19, 2026
@wscurran
Copy link
Copy Markdown
Contributor

Thanks for fixing the onboard process and ensuring that it handles reruns gracefully, this will definitely improve the user experience for users who encounter installation issues.

@wscurran wscurran added Getting Started Use this label to identify setup, installation, or onboarding issues. priority: high Important issue that should be resolved in the next release labels Mar 19, 2026
@miyoungc
Copy link
Copy Markdown
Contributor

This PR has gotten stale. The issue seems addressed as part of #229.
Closing this PR. Thanks for your contribution effort.

@miyoungc miyoungc closed this Mar 20, 2026
mafueee pushed a commit to mafueee/NemoClaw that referenced this pull request Mar 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working Getting Started Use this label to identify setup, installation, or onboarding issues. NemoClaw CLI Use this label to identify issues with the NemoClaw command-line interface (CLI). priority: high Important issue that should be resolved in the next release

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Make nemoclaw onboard robust when rerun after a failed install instead of requiring uninstall.sh as a workaround

3 participants