maemachinebroke/hakurei
1
0
Fork 0
forked from security/hakurei
Code Pull Requests Activity

internal/pipewire: treat noAck violation as fatal

Browse Source 
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:
Ophestra
2025-12-13 22:30:06 +09:00
parent b5999b8814
commit de0467a65e
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
internal/pipewire/core.go
View File

@@ -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.