Fix PC-assisted Robot Hardware installation - #155
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Outcome
PC-assisted managed devices now receive a pinned Robot Hardware source and aarch64/x86_64 Python dependency bundle from the editor computer. Install Hardware no longer requires the target device to reach GitHub or PyPI, and it reuses the managed Python 3.11 environment.
The installer also recognizes and cleans the incomplete blacknode-robot clone left by a failed download while refusing to touch unrelated directories.
Verification
Managed Runtime release decision
No Runtime release is required. This changes the editor-server SSH orchestration behind the existing Install Hardware action; it does not change the managed Runtime service, API, installer, supervision, or package-sync contract. The editor/core release delivers the fix.