internal/pipewire: treat noAck violation as fatal
All checks were successful
Test / Create distribution (push) Successful in 52s
Test / Sandbox (push) Successful in 2m52s
Test / Sandbox (race detector) (push) Successful in 4m56s
Test / Hpkg (push) Successful in 5m0s
Test / Hakurei (race detector) (push) Successful in 5m51s
Test / Hakurei (push) Successful in 2m50s
Test / Flake checks (push) Successful in 2m3s
All checks were successful
Test / Create distribution (push) Successful in 52s
Test / Sandbox (push) Successful in 2m52s
Test / Sandbox (race detector) (push) Successful in 4m56s
Test / Hpkg (push) Successful in 5m0s
Test / Hakurei (race detector) (push) Successful in 5m51s
Test / Hakurei (push) Successful in 2m50s
Test / Flake checks (push) Successful in 2m3s
Receiving this event indicates something has gone terribly wrong somehow, and ignoring Core::BoundProps causes inconsistent state anyway. Signed-off-by: Ophestra <cat@gensokyo.uk>
This commit is contained in:
@@ -332,7 +332,7 @@ var ErrBadBoundProps = errors.New("attempting to store bound props on a proxy th
|
|||||||
type noAck struct{}
|
type noAck struct{}
|
||||||
|
|
||||||
// setBoundProps should never be called as this proxy should never be targeted by [CoreBoundProps].
|
// 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
|
// ErrBadRemove is returned when a [CoreRemoveId] event targeting a proxy
|
||||||
// that should never be targeted is received and processed.
|
// that should never be targeted is received and processed.
|
||||||
|
|||||||
Reference in New Issue
Block a user