801 Commits

Author	SHA1	Message	Date
cat	6d0d9cecd1	internal/pipewire: handle nil spa_dict correctly ... This now marshals into a value of type None when the slice is nil, and correctly unmarshals from type None. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 07:12:00 +09:00
cat	17248d7d61	internal/pipewire: unmarshal nil pointer correctly ... This now calls unmarshalCheckTypeBounds to advance to the next message. Additionally, handling for None value is relocated to a function for reuse by other types. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 06:58:53 +09:00
cat	41e5628c67	internal/pipewire: return correct size for nil spa_dict ... A nil spa_dict results in a None type value being sent over the wire. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 06:07:46 +09:00
cat	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
cat	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
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	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
cat	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
cat	b72d502f1c	internal/outcome: populate instance metadata for PipeWire ... These have similar semantics to equivalent Wayland security-context-v1 fields. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-10 03:01:30 +09:00
cat	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
cat	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
cat	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
cat	c538df7daa	internal/pipewire: expose connection props ... Unused in hakurei but could be useful when the package is moved out of internal. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 06:51:12 +09:00
cat	44e5aa1a36	internal/pipewire: include remaining size in recvmsg wrapper ... This otherwise truncates the received data by len(remaining) bytes. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 06:36:46 +09:00
cat	cf0e7d8c27	internal/pipewire: reset per-roundtrip state once per call ... This was left in consume when relocating per-roundtrip code out of the per-receive consume method. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 06:28:33 +09:00
cat	130add21e5	internal/pipewire: increment remote sequence after establishing bounds ... This avoids incrementing it twice proceeding from a partial message. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 06:21:41 +09:00
cat	5ec4045e24	internal/pipewire: do not clobber error parsing SCMs ... The error is handled later, clobbering it here breaks error handling when SCMs are present. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 06:02:15 +09:00
cat	be2075f169	Revert "internal/pipewire: work around remote sequence quirk" ... This reverts commit 564db6863b.	2025-12-09 05:25:41 +09:00
cat	564db6863b	internal/pipewire: work around remote sequence quirk ... Remote sequence sometimes start with a non-zero value, and keeps the same value for a while before going back to zero. Conditions for reproducing this behaviour is not yet known. This change works around this behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 20:10:01 +09:00
cat	87781c7658	treewide: include PipeWire op and enforce PulseAudio check ... This fully replaces PulseAudio with PipeWire and enforces the PulseAudio check and error message. The pipewire-pulse daemon is handled in the NixOS module. Closes #26. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 08:53:04 +09:00
cat	0c38fb7b6a	hst: expose daemon as fs entry ... This is slightly counterintuitive, but it turned out well under this framework since the daemon backs its target file. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 07:38:47 +09:00
cat	c8eeb4a4d1	internal/outcome: integrate pipewire server ... This is very simple and takes almost no inputs. This is not yet hooked up to anything to prevent breaking any existing behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 05:03:16 +09:00
cat	bf856f06e5	internal/pipewire: constant for PIPEWIRE_REMOTE ... This is not defined anywhere in upstream PipeWire, no idea why. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 23:35:29 +09:00
cat	1931b54600	hst: add pipewire flag ... These are for #26. None of them are implemented yet. This fixes up test cases for the change to happen. Existing source code and JSON configuration continue to have the same effect. Existing flags get its EPulse bit replaced by EPipeWire. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 22:34:40 +09:00
cat	093e30c788	internal/system: integrate PipeWire SecurityContext ... Tests for this Op happens to be the best out of everything due to the robust infrastructure offered by internal/pipewire. This is now ready to use in internal/outcome for implementing #26. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 17:39:34 +09:00
cat	1b17ccda91	internal/system: optional op check parallelism ... The PipeWire Op check cannot be made parallel due to the OS interaction. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 17:31:10 +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	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
cat	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
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	246e04214a	internal/system: pass syscall error message ... This makes wrapped syscall errors produce a cleaner error message. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 02:08:05 +09:00
cat	503bfc6468	internal/system: port connect by name ... This behaviour is a bit messy and checks what appears to be a windows-specific environment variable for some reason. Keeping everything intact regardless to match upstream behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 02:00:19 +09:00
cat	d837628b4c	internal/system: remove ineffectual join reverting wayland ... Removing the pathname socket used to be handled separately, now it is done during the Close call. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-07 00:43:50 +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	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
cat	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
cat	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
cat	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
cat	490093a659	internal/pipewire: set errno on an empty message ... This matches upstream behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 16:50:49 +09:00
cat	2b22efcdf1	internal/pipewire: rename context consume method ... This name is more correct since it does not roundtrip, but receives messages. This is also more consistent with the method on event proxies. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-06 16:44:39 +09:00
cat	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
cat	0d3f332d45	internal/pipewire: do not send ancillary msg without files ... This is unnecessary and does not match upstream behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-05 04:20:04 +09:00
cat	d5509cc6e5	internal/pipewire: constants from pipewire/keys.h ... 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>	2025-12-05 03:27:30 +09:00
cat	0d3ae6cb23	internal/pipewire: improve protocol error messages ... These are mostly small formatting changes, with the biggest change being to UnexpectedEOFError where its kind is now described as part of the error type. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-04 03:15:58 +09:00
cat	69b1131d66	internal/pipewire: use type name in error strings ... This provides more useful messages for protocol errors. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-04 02:29:27 +09:00
cat	2c0b92771a	internal/pipewire: relocate constants ... This should make things easier to navigate, and possible to fully automatically generate the constants in the future. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-03 03:52:17 +09:00
cat	054c91879f	internal/pipewire: finalizers for dangling files ... This makes their handling much less error-prone. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-03 03:36:02 +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	32fb137bb2	internal/pipewire: fail on unacknowledged proxies ... These proxies (with special cases documented in the implementation) are only safe for use after acknowledgement from the server. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-02 21:17:46 +09:00