fortify

Author	SHA1	Message	Date
Ophestra	24618ab9a1	sandbox: move out of internal All checks were successful Test / Create distribution (push) Successful in 18s Details Test / Fpkg (push) Successful in 2m40s Details Test / Data race detector (push) Successful in 3m13s Details Test / Fortify (push) Successful in 3m1s Details Test / Flake checks (push) Successful in 51s Details Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-03-17 02:55:36 +09:00
Ophestra	9ce4706a07	sandbox: move params setup functions All checks were successful Test / Create distribution (push) Successful in 25s Details Test / Fortify (push) Successful in 2m37s Details Test / Fpkg (push) Successful in 3m30s Details Test / Data race detector (push) Successful in 4m8s Details Test / Flake checks (push) Successful in 57s Details Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-03-17 02:48:32 +09:00
Ophestra	673b648bd3	cmd/fpkg: call app in-process All checks were successful Test / Create distribution (push) Successful in 28s Details Test / Fortify (push) Successful in 2m31s Details Test / Data race detector (push) Successful in 3m25s Details Test / Fpkg (push) Successful in 3m29s Details Test / Flake checks (push) Successful in 55s Details Wrapping fortify is slow, painful and error-prone. Start apps in-process instead. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-02-26 19:51:44 +09:00
Ophestra	29c38caac8	app/shim/manager: return error on bad fsu path All checks were successful Test / Create distribution (push) Successful in 24s Details Test / Run NixOS test (push) Successful in 2m9s Details This results in a graceful failure that does not leave garbage behind. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-02-16 18:59:45 +09:00
Ophestra	e599b5583d	fmsg: implement suspend in writer All checks were successful Test / Create distribution (push) Successful in 24s Details Test / Run NixOS test (push) Successful in 2m18s Details This removes the requirement to call fmsg.Exit on every exit path, and enables direct use of the "log" package. However, fmsg.BeforeExit is still encouraged when possible to catch exit on suspended output. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-02-16 18:51:53 +09:00
Ophestra	33a4ab11c2	internal: move shim and init into app All checks were successful Test / Create distribution (push) Successful in 24s Details Test / Run NixOS test (push) Successful in 2m7s Details This structure makes more sense, as both processes are part of an app's lifecycle. Signed-off-by: Ophestra <cat@gensokyo.uk>	2025-02-16 16:28:46 +09:00

6 Commits