1335 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Ophestra	0c0e3d6fc2	hst: add direct hardware option ... This is unfortunately the only possible setup to securely expose PipeWire to the container. Further explanation explained in the doc comment and #29. This will be implemented in a future commit. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-15 12:29:32 +09:00
Ophestra	fae910a1ad	container: sync stubbed wait4 loop after notify ... This ensures consistent state observed by wait4 loop when running against stub. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 10:22:48 +09:00
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
Ophestra	30dcab0734	internal/pipewire: SecurityContext as destructible ... This proxy can be destroyed by sending a Core::Destroy targeting it. This change implements the Destroy method by embedding destructible. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 09:31:50 +09:00
Ophestra	0ea051062b	internal/pipewire: reorder context struct ... This change reorders and groups struct elements. This improves readability since this struct holds a lot of state loosely related to each other. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 09:26:30 +09:00
Ophestra	b0f2ab6fff	internal/pipewire: implement Core::Destroy ... 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>	2025-12-14 09:20:58 +09:00
Ophestra	00a5bdf006	internal/pipewire: do not emit None for spa_dict ... Turns out the PipeWire server does not expect a value of type None here at all. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-14 09:06:44 +09:00
Ophestra	a27dfdc058	internal/pipewire: implement Core::CreateObject ... 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>	2025-12-14 08:10:57 +09:00
Ophestra	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
Ophestra	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
Ophestra	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
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	ebc67bb8ad	nix: update flake lock ... NixOS 25.11 introduces a crash in cage and an intermittent crash in foot. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-12 08:39:55 +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	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
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	ccc0d98bd7	release: 0.3.2 ... Signed-off-by: Ophestra <cat@gensokyo.uk> v0.3.2	2025-12-09 08:12:52 +09:00
Ophestra	a3fd05765e	container: load initial process started before syscall ... This avoids a race between returning from syscall and checking the state. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-09 08:12:22 +09:00
Ophestra	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
Ophestra	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
Ophestra	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
Ophestra	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
Ophestra	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
Ophestra	be2075f169	Revert "internal/pipewire: work around remote sequence quirk" ... This reverts commit 564db6863b.	2025-12-09 05:25:41 +09:00
Ophestra	e9fb1d7be5	container/initdaemon: copy wstatus from wait4 loop ... Due to the special nature of the init process, direct use of wait outside the wait4 loop is racy. This change copies the wstatus from wait4 loop state instead. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:58:42 +09:00
Ophestra	dafe9f8efc	container: spin instead of block on wait4 ECHILD ... Blocking prevents further wait4 processing causing ops to never receive their signals. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:56:13 +09:00
Ophestra	96dd7abd80	container: improve error message fallback ... This now falls back to message.Error if no other concrete type is matched. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:45:54 +09:00
Ophestra	d5fb179012	cmd/hakurei: exec instead of fork/exec from shell ... There is no reason to keep the shell process around. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:29:41 +09:00
Ophestra	462863e290	container: friendlier error message for op timing out ... This includes the string for the failing op which helps with troubleshooting. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:19:03 +09:00
Ophestra	2786611b88	test/interactive: add app with bad daemon ... This is useful for testing daemon error handling behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 22:12:07 +09:00
Ophestra	791a1dfa55	container: make wait4 loop available to ops ... Due to the special nature of the init process, regular wait calls are unavailable. This change provides infrastructure to access wait4 loop state from Op. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 21:43:49 +09:00
Ophestra	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
Ophestra	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
Ophestra	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
Ophestra	357cfcddee	container: start daemons within container ... This is useful for daemons internal to the container. The only current use case is pipewire-pulse. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 07:21:04 +09:00
Ophestra	6bf245cf1b	container: pass context as setup state ... This is useful currently for daemon Op, but could be used for many other things. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 06:06:19 +09:00
Ophestra	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
Ophestra	5785714b64	container: call op method right before initial process ... This is at a point considered to be already "within" the container. Daemons internal to the container can be started here. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 04:57:24 +09:00
Ophestra	422efcf258	hst: check for insecure PulseAudio enablement ... This is currently still a noop, but required for #26. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 03:13:02 +09:00
Ophestra	104eeecf65	cmd/hakurei: add pipewire flag ... This is for "run" command, formerly permissive defaults behaviour. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-12-08 02:39:55 +09:00
Ophestra	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
Ophestra	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
Ophestra	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
Ophestra	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