Repository navigation
WIRE native: preserve EdgeId across legacy OUT selector retarget and same-target replug - #380
Closed
masarray wants to merge 4 commits into
Conversation
Owner
Author
|
Reconciled into canonical ENGINE #266 via merged #379 ( |
This was referenced Nov 4, 2026
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.
Stacked regression on #379, preserving exact-head Windows CI already running there. Existing ChannelSendRef.primaryOutput updates now retain the same stable
edgeIdwhen changing/confirming a target, rather than erasing/recreating an edge that another WIRE/Navigator selection is tracking. Native PCM test confirms unchanged channel sample index/level after same-target and serial retarget and no ID churn. No CSS, other engine or callback created. Only merge AFTER parent #379 integrated to sole ENGINE owner #266 and this head's CTest passes; no Windows hardware or production-v8 GUI claims.