dohertj2/lmxopcua
1
0
Fork 0
Code Issues 8 Pull Requests Actions Packages Projects Releases Wiki Activity

feat(raw): hot-rebind a renamed raw tag's live value without a node recreate #489

New Issue
Open
opened 2026-07-21 03:36:41 -04:00 by dohertj2 · 0 comments
dohertj2 commented 2026-07-21 03:36:41 -04:00
Owner
Copy Link
Copy Source

Deferred follow-up from v3 Batch 4 (docs/plans/2026-07-16-v3-batch4-PR.md).

Renaming a raw tag correctly rewrites the address space on deploy — the old raw NodeId goes, the new one appears, and the planner re-points the referencing UNS node. This was live-verified during the Batch 4 gate (HR200 → HR200X).

But the renamed tag's live value does not rebind until the node is recreated/restarted. Current operational workaround is deploy-THEN-recreate, which is documented but is a sharp edge: an operator who renames a tag and does not restart sees a materialised node that never receives data.

Related sharp edge recorded in the same gate: an absolute RawPath script literal pointing at the old name correctly fails Bad 0x80000000 after the rename — that part is working as intended and is a separate concern from the value rebind.

Deferred follow-up from v3 Batch 4 (`docs/plans/2026-07-16-v3-batch4-PR.md`). Renaming a raw tag correctly rewrites the address space on deploy — the old raw NodeId goes, the new one appears, and the planner re-points the referencing UNS node. This was live-verified during the Batch 4 gate (`HR200` → `HR200X`). **But the renamed tag's live value does not rebind until the node is recreated/restarted.** Current operational workaround is deploy-THEN-recreate, which is documented but is a sharp edge: an operator who renames a tag and does not restart sees a materialised node that never receives data. Related sharp edge recorded in the same gate: an **absolute** RawPath script literal pointing at the old name correctly fails `Bad 0x80000000` after the rename — that part is working as intended and is a separate concern from the value rebind.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
auto-managed
queue management
 cross-driver
queue management
 driver/abcip
queue management
 driver/ablegacy
queue management
 driver/focas
queue management
 driver/opcuaclient
queue management
 driver/s7
queue management
 driver/twincat
queue management
 phase/1
queue management
 phase/2
queue management
 phase/3
queue management
 phase/4
queue management
 phase/5
queue management
 phase/6
queue management
 queue/blocked
queue management
 queue/done
queue management
 queue/failed
queue management
 queue/in-progress
queue management
 queue/queued
queue management
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
dohertj2 (dohertj2)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dohertj2/lmxopcua#489
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?