36 Commits

Author	SHA1	Message	Date
Ophestra	ffbec828e1	internal/pipewire: move Core wrapper methods under Core ... These do not belong under Context, and is an early implementation limitation that carried over. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 05:37:21 +09:00
Ophestra	de0467a65e	internal/pipewire: treat noAck violation as fatal ... 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>	2025-12-13 22:30:06 +09:00
Ophestra	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
Ophestra	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
Ophestra	47db461546	internal/pipewire: generic Core::Error handling ... This flushes message buffer before queueing the event expecting the error. Since this is quite useful and relatively complex, it is relocated to a method of Context. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-11 04:07:55 +09:00
Ophestra	0a3fe5f907	internal/pipewire: export Registry::Destroy ... This handles the error returned by Sync. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-11 03:34:33 +09:00
Ophestra	f8b3db3f66	internal/pipewire: cleaner error message for unsupported type ... The error string itself is descriptive enough, so use it as the error message directly. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-10 01:51:06 +09:00
Ophestra	0e2fb1788f	internal/pipewire: implement Registry::Destroy ... 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>	2025-12-10 01:25:30 +09:00
Ophestra	d8417e2927	internal/pipewire: implement Registry::GlobalRemove ... 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>	2025-12-10 01:00:03 +09:00
Ophestra	8cdd659239	internal/pipewire: seq access method for consume ... This improves readability as the offset is not immediately obvious. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 17:07:30 +09:00
Ophestra	15c2839a09	internal/pipewire: respond to Core::Ping ... There is currently no known message that will get the PipeWire server to emit this event. It should be handled regardless. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 14:55:56 +09:00
Ophestra	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
Ophestra	bb1fc4c7bc	internal/pipewire: check pending ids after done ... This is not guaranteed to have completed after a roundtrip. This is leftover from when Roundtrip also sent and waited for sync. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 21:09:55 +09:00
Ophestra	f44923da29	internal/pipewire: post-sync cleanup functions ... This makes it easier to handle resources who only needs to stay alive before the next sync. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 21:03:21 +09:00
Ophestra	7cb3308a53	internal/pipewire: store proxy errors in context ... This change fixes handling of non-fatal errors during a roundtrip as there can be multiple receive calls per roundtrip. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 19:13:46 +09:00
Ophestra	8a2f9edcf9	internal/pipewire: use sendmsg/recvmsg directly ... The PipeWire protocol does not work with Go abstractions. This change makes relevant methods call sendmsg/recvmsg directly. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 02:12:47 +09:00
Ophestra	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
Ophestra	e7a665e043	internal/pipewire: handle Core::Error ... This event is not encountered in the pw-container sample, but already has existing sample from an excerpt. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-02 06:16:18 +09:00
Ophestra	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
Ophestra	647aa9d02f	internal/pipewire: preallocate for footer ... This is useful during serialisation. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-02 03:06:27 +09:00
Ophestra	3d4c7cdd9e	internal/pipewire: implement Core::Error ... Sample was captured from pw-cli. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-30 01:39:39 +09:00
Ophestra	4fd6d6c037	internal/pipewire: implement Core::Ping, Core::Pong ... I could not get the server to produce these events, however I am confident enough with the implementation to do it by hand. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-29 23:25:29 +09:00
Ophestra	5a5c4705dd	internal/pipewire: implement Registry::Bind ... This change also adds test cases for messages before this one. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-29 03:01:53 +09:00
Ophestra	f703aa20a5	internal/pipewire: implement client generation footer ... This corresponds with the core generation footer and seem to be the only other possible footer type. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-29 02:55:30 +09:00
Ophestra	5c12425d48	internal/pipewire: implement Registry::Global ... Dealing with this event reawakened my burning hatred for OOP. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-28 02:32:45 +09:00
Ophestra	cbe86dc4f0	internal/pipewire: add json struct tags ... These match the names found in documentation. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-28 01:33:32 +09:00
Ophestra	e028a61fc1	internal/pipewire: preallocate for known size ... This is still not efficient by any means, but it should eliminate most non-reflect allocation (all allocation if PODMarshaler is not used). Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-27 02:26:31 +09:00
Ophestra	73987be7d4	internal/pipewire: size without serialisation ... This is required to achieve zero allocation (other than reflect). Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-27 02:17:38 +09:00
Ophestra	2698ca00e8	internal/pipewire: implement Core::Done ... The message in the sample does not correspond to any known method call. The spec does not mention what to do with messages like this, but all existing usage code simply drops it. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-26 19:02:21 +09:00
Ophestra	1d0143386d	internal/pipewire: optional final trailing garbage check ... Omitting the check is only useful for custom unmarshaler. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-26 18:50:39 +09:00
Ophestra	77f5b89a41	internal/pipewire: implement Core::BoundProps ... Very straightforward type, everything is already supported. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 18:40:19 +09:00
Ophestra	cfeb7818eb	internal/pipewire: implement Core::Info and generation footer ... These are not directly related but are first encountered on the same message in the capture. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 15:16:12 +09:00
Ophestra	fc3d78fe01	internal/pipewire: implement Core::Sync ... Once again, already entirely supported, the offset is not yet fully verified but makes intuitive sense. Will verify this on future occurrences of the message. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 08:52:06 +09:00
Ophestra	591637264a	internal/pipewire: implement Core::GetRegistry ... This struct is entirely supported, so this change is very straightforward. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 08:34:19 +09:00
Ophestra	8f4a3bcf9f	internal/pipewire: use custom marshaler when available ... This reduces special cases. This change also exposes unmarshalled message size on the wire. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 04:05:22 +09:00
Ophestra	5bcafcf734	internal/pipewire: implement Core::Hello ... This implements enough types to correctly marshal and unmarshal Core::Hello. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-11-25 01:20:30 +09:00