Ophestra 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

..

testdata

internal/pipewire: store sample iovec continuously

2025-11-28 00:35:10 +09:00

client_test.go

internal/pipewire: seq access method for consume

2025-12-07 17:07:30 +09:00

client.go

internal/pipewire: implement Core::RemoveId

2025-12-13 21:50:32 +09:00

core_test.go

internal/pipewire: implement Core::Destroy

2025-12-14 09:20:58 +09:00

core.go

internal/pipewire: implement Core::Destroy

2025-12-14 09:20:58 +09:00

header_test.go

internal/pipewire: implement Core::Error

2025-11-30 01:39:39 +09:00

header.go

internal/pipewire: implement client context

2025-12-02 06:03:21 +09:00

pipewire_test.go

internal/pipewire: handle SecurityContext::Create error

2025-12-14 09:41:28 +09:00

pipewire.go

internal/pipewire: reorder context struct

2025-12-14 09:26:30 +09:00

pod_test.go

internal/pipewire: improve protocol error messages

2025-12-04 03:15:58 +09:00

pod.go

internal/pipewire: do not emit None for spa_dict

2025-12-14 09:06:44 +09:00

securitycontext_test.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00

securitycontext.go

internal/pipewire: handle SecurityContext::Create error

2025-12-14 09:41:28 +09:00

spa_test.go

internal/pipewire: use type name in error strings

2025-12-04 02:29:27 +09:00

spa.go

internal/pipewire: constants from pipewire/keys.h

2025-12-05 03:27:30 +09:00