hakurei/internal/pipewire/core_test.go, branch developlow-level userspace tooling for Rosa OShttp://src.rosa.moe/hakurei/atom/internal/pipewire/core_test.go?h=develop2025-12-14T00:20:58Zinternal/pipewire: implement Core::Destroy2025-12-14T00:20:58ZOphestracat@gensokyo.uk2025-12-14T00:20:58Zurn:sha1:b0f2ab6fffd48580d758de80165f8d97438b4066
This change also implements pending destructible check on Sync. Destruction method should always be implemented as a wrapper of destructible.destroy.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: do not emit None for spa_dict2025-12-14T00:06:44ZOphestracat@gensokyo.uk2025-12-14T00:06:44Zurn:sha1:00a5bdf006ba800e0797ff4c2b732e5df4fa28ff
Turns out the PipeWire server does not expect a value of type None here at all.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Core::CreateObject2025-12-13T23:10:57ZOphestracat@gensokyo.uk2025-12-13T23:10:57Zurn:sha1:a27dfdc058caf4ca0578a7cf98282c1998c94e6b
Nothing uses this right now, this would have to be called by wrapper methods on Registry that would search the objects
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Core::RemoveId2025-12-13T12:50:32ZOphestracat@gensokyo.uk2025-12-13T12:49:28Zurn:sha1:b5999b88140eb437e87580848513dc1e74bc190b
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>
internal/pipewire: implement Registry::Destroy2025-12-09T16:25:30ZOphestracat@gensokyo.uk2025-12-09T16:25:30Zurn:sha1:0e2fb1788f48540fd7a860b8c571e3a8c1cae756
This requires error handling infrastructure in Core that does not yet exist, so it is not exported for now. It has been manually tested via linkname against PipeWire.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement Registry::GlobalRemove2025-12-09T16:00:03ZOphestracat@gensokyo.uk2025-12-09T15:59:01Zurn:sha1:d8417e292762eebbbe7203aa98eb34eb5c34434e
This is emitted by PipeWire when a global object disappears, because PipeWire insists that all clients that had called Core::GetRegistry must constantly sync its local registry state with the remote.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: seq access method for consume2025-12-07T08:07:30ZOphestracat@gensokyo.uk2025-12-07T08:07:30Zurn:sha1:8cdd659239654aa2c18e392d5cde3c31da069b98
This improves readability as the offset is not immediately obvious.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: constants from pipewire/keys.h2025-12-04T18:27:30ZOphestracat@gensokyo.uk2025-12-04T18:27:22Zurn:sha1:d5509cc6e54282f048389d8dcfd731fa5a4f3b09
These are PipeWire spa_dict keys. Interestingly many keys in the sample are undefined and appear as magic strings in upstream source code.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: use type name in error strings2025-12-03T17:29:27ZOphestracat@gensokyo.uk2025-12-03T17:27:45Zurn:sha1:69b1131d6622108f37c85014035f71cf4f2986e5
This provides more useful messages for protocol errors.
Signed-off-by: Ophestra <cat@gensokyo.uk>
internal/pipewire: implement client context2025-12-01T21:03:21ZOphestracat@gensokyo.uk2025-12-01T21:03:21Zurn:sha1:af741f20a003d48863eb5e9f7cf71052abd4116d
This consumes the entire sample, is validated to send identical messages and correctly handle received messages.
Signed-off-by: Ophestra <cat@gensokyo.uk>