state: resolving an alert fails with invalid UTF8 byte 0x00 #1316

Closed
opened 2026-10-27 13:39:54 +00:00 by sam · 0 comments
Owner

Since operator alerts merged, the State Store fails to resolve alerts with 'invalid byte sequence for encoding "UTF8": 0x00', so condition alerts never clear. A NUL byte reaches a text column, likely from a key or body built with a zero separator. Done when alerts resolve on a running stack and the alert key cannot carry a NUL.

Close reason

Lock key quoted; NUL escaped. Regression test added.


Imported from beads archie-core-fh2bc · GitHub #1651 · type bug · priority P1 · created 2026-10-11 · closed 2026-10-12

Since operator alerts merged, the State Store fails to resolve alerts with 'invalid byte sequence for encoding "UTF8": 0x00', so condition alerts never clear. A NUL byte reaches a text column, likely from a key or body built with a zero separator. Done when alerts resolve on a running stack and the alert key cannot carry a NUL. ### Close reason Lock key quoted; NUL escaped. Regression test added. --- _Imported from beads `archie-core-fh2bc` · GitHub #1651 · type bug · priority P1 · created 2026-10-11 · closed 2026-10-12_
sam added the highbug labels 2026-10-27 13:39:54 +00:00
sam self-assigned this 2026-10-27 13:39:54 +00:00
sam closed this issue 2026-10-27 13:39:54 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1316