From de0467a65ef15108cd6d6513e3ed07b7704f3819 Mon Sep 17 00:00:00 2001 From: Ophestra Date: Sat, 13 Dec 2025 22:30:06 +0900 Subject: [PATCH] internal/pipewire: treat noAck violation as fatal Receiving this event indicates something has gone terribly wrong somehow, and ignoring Core::BoundProps causes inconsistent state anyway. Signed-off-by: Ophestra --- internal/pipewire/core.go | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/internal/pipewire/core.go b/internal/pipewire/core.go index 3d103d6..ff13eab 100644 --- a/internal/pipewire/core.go +++ b/internal/pipewire/core.go @@ -332,7 +332,7 @@ var ErrBadBoundProps = errors.New("attempting to store bound props on a proxy th type noAck struct{} // setBoundProps should never be called as this proxy should never be targeted by [CoreBoundProps]. -func (noAck) setBoundProps(*CoreBoundProps) error { return ErrBadBoundProps } +func (noAck) setBoundProps(*CoreBoundProps) error { panic(ErrBadBoundProps) } // ErrBadRemove is returned when a [CoreRemoveId] event targeting a proxy // that should never be targeted is received and processed.