10 Commits

Include renames

Author	SHA1	Message	Date
cat	178c8bc28b	internal/pipewire: handle SecurityContext::Create error ... This method can result in an error targeting it, so it is handled here. This change also causes a call to Create to also Core::Sync, as it should have done. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 09:41:28 +09:00
cat	30dcab0734	internal/pipewire: SecurityContext as destructible ... This proxy can be destroyed by sending a Core::Destroy targeting it. This change implements the Destroy method by embedding destructible. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 09:31:50 +09:00
cat	b5999b8814	internal/pipewire: implement Core::RemoveId ... This is emitted by the server when a proxy id is removed for any reason. Currently, the only path for this to be emitted is when a global object is destroyed while some proxy is still bound to it. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-13 21:50:32 +09:00
cat	e60ff660f6	internal/pipewire: treat unknown opcode as fatal ... Skipping events can cause local state to diverge from the server. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-11 04:22:03 +09:00
cat	7c6fc1128b	internal/pipewire: set finalizer on scc ... This prevents leaking the socket and pipe fds. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 17:29:22 +09:00
cat	b9b9705b52	internal/pipewire: specify opcode and file count with message ... This adds checking of FileCount while writing a message. Message encoding is relocated to an exported method to be used externally, probably for test stubbing. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 13:54:11 +09:00
cat	3cb58b4b72	internal/pipewire: high level SecurityContext helper ... This sets up close pipe and socket internally, and exposes the resulting pathname socket and close_fd cleanup as an io.Closer. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 21:16:27 +09:00
cat	c34439fc5f	internal/pipewire: collect non-protocol errors ... These errors are recoverable and should not terminate event handling. Only terminate event handling for protocol errors or inconsistent state that makes further event handling impossible. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-03 01:35:43 +09:00
cat	af741f20a0	internal/pipewire: implement client context ... This consumes the entire sample, is validated to send identical messages and correctly handle received messages. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-02 06:03:21 +09:00
cat	de3fc7ba38	internal/pipewire: implement SecurityContext::Create ... This is finally the thing we are after. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-29 16:46:39 +09:00