Repository navigation
feat!: migrate operator-controls to Forge 2.x and Dora 1.x - #3
Merged
Merged
Conversation
mrgh97
marked this pull request as ready for review
November 12, 2026 08:54
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.
Migrate operator-controls to the Forge 2.x / Dora 1.x deployment baseline.
BREAKING CHANGE: Deploy matching Forge packages, Dora CLI/coordinator/daemon, this node and all connected peer nodes together. Rebuild executable artifacts for that environment. Do not replace a single node in a Forge 1.x / Dora 0.4.x graph. Retain stable/1.x for the previous stack.
本次为 breaking change:节点对接前需对齐 Forge、Dora 和上下游节点版本,并重新构建部署产物;旧 Forge 1.x / Dora 0.4.x 数据流不支持只替换单节点。
Python baseline: Msgs 2.1.0 / Pillow 13.0.0 / Common 2.1.0; applicable Robot, Policy, Kinematics and Tool families remain 2.0.0. Dora is 1.0.1. Forge families version independently. Rust Msgs stays at the published 2.0.0 crate; forge_msgs.v1 is unchanged.
Changes in this update:
Validation this round:
Reviewed report with actual per-node/chain Dora commands and results (original logs retained locally): migration/msgs-2.1.0-report.json. Every new multi-node graph includes adapter-forge-gateway.
Remaining: Applicable actual hardware/model, final supported-platform artifacts, sustained run and rollback acceptance remain pending.
The 640x480 generated RGB/depth chain with Viewer, Rust sinks and Gateway passed one 10-second run this round (284 frames per stream). This does not close the historical intermittent 64 MiB daemon reply issue, sustained-run or physical camera acceptance.
Pending; software checks, fake/dummy backends and negative prerequisite records are scoped evidence only. Every new multi-node graph contains adapter-forge-gateway.
GitLab synchronization remains pending full acceptance. Existing personal-fork PR source branches are updated in place; no upstream development branch is created.