Ophestra 5e7861bb00 internal/pipewire: handle dangling files in roundtrip ...

This should not be handled on every receive as it could cause valid (though impossible in current upstream implementation) messages to be rejected and raise a protocol error.

Signed-off-by: Ophestra <cat@gensokyo.uk>

2025-12-06 19:21:57 +09:00

..

testdata

internal/pipewire: store sample iovec continuously

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

client_test.go

internal/pipewire: constants from pipewire/keys.h

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

client.go

internal/pipewire: collect non-protocol errors

2025-12-03 01:35:43 +09:00

core_test.go

internal/pipewire: constants from pipewire/keys.h

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

core.go

internal/pipewire: store proxy errors in context

2025-12-06 19:13:46 +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: use sendmsg/recvmsg directly

2025-12-06 02:12:47 +09:00

pipewire.go

internal/pipewire: handle dangling files in roundtrip

2025-12-06 19:21:57 +09:00

pod_test.go

internal/pipewire: improve protocol error messages

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

pod.go

internal/pipewire: improve protocol error messages

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

securitycontext_test.go

internal/pipewire: constants from pipewire/keys.h

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

securitycontext.go

internal/pipewire: collect non-protocol errors

2025-12-03 01:35:43 +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