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

OpcUaClient first sight of an inactive+acked upstream condition is told as Unspecified, not a flagged Clear #658

New Issue
Closed
opened 2026-10-09 04:31:11 -04:00 by dohertj2 · 1 comment
dohertj2 commented 2026-10-09 04:31:11 -04:00
Owner
Copy Link
Copy Source

Found by the hw4 re-review of #611 (ALMA projection), pre-existing on master.

On first sight (no prior told state, e.g. after a driver respawn) an upstream condition that is inactive + acked is emitted as AlarmTransitionKind.Unspecified rather than as a flagged (IsRestatement) Clear.

Consequences:

  • A host condition retained Active across the respawn stays Active (nothing clears it).
  • When the host has no active prior, NativeAlarmProjector takes the default branch and writes an "Activated" /alerts row for an alarm that is inactive.

Expected: first sight of inactive+acked → flagged Clear (no row when the host condition is already inactive, a real Clear when it was retained Active).

Related: #656 (IsRestatement), #657 (respawn replays inactive+unacked as Raise+Clear). Likely fixed together with #657.

Filed 2026-10-09 from the hw4 batch review (reports/alma-rereview.md F4).

Found by the hw4 re-review of #611 (ALMA projection), pre-existing on master. On first sight (no prior told state, e.g. after a driver respawn) an upstream condition that is **inactive + acked** is emitted as `AlarmTransitionKind.Unspecified` rather than as a flagged (`IsRestatement`) `Clear`. Consequences: - A host condition retained **Active** across the respawn stays Active (nothing clears it). - When the host has no active prior, `NativeAlarmProjector` takes the default branch and writes an **"Activated"** `/alerts` row for an alarm that is inactive. Expected: first sight of inactive+acked → flagged Clear (no row when the host condition is already inactive, a real Clear when it was retained Active). Related: #656 (IsRestatement), #657 (respawn replays inactive+unacked as Raise+Clear). Likely fixed together with #657. _Filed 2026-10-09 from the hw4 batch review (reports/alma-rereview.md F4)._
dohertj2 commented 2026-10-09 04:55:27 -04:00
Author
Owner
Copy Link
Copy Source

Duplicate of #657 (its item 2: OpcUaClient first sight of an inactive+acked condition). Closing; the extra detail from this report is copied to #657.

Duplicate of #657 (its item 2: OpcUaClient first sight of an inactive+acked condition). Closing; the extra detail from this report is copied to #657.
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/mqtt
MQTT / Sparkplug B broker-subscribe driver
 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#658
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?