You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit c33e646
Browse filesBrowse the repository at this point in the historyBrowse files
fix(fspy): run processes untracked when injection fails
In restricted sandboxes that deny the seccomp syscall, every spawn in a
cached task failed with EPERM: the preload installs a seccomp
user-notification filter before exec'ing a static binary, the install was
refused, and the interposed exec returned the error instead of running
the program.
Tracking must never break the traced process. The exec and posix_spawn
hooks now mark the run's trace incomplete and execute untracked with the
original arguments when injection fails. The preload constructor no
longer aborts the host process on a missing or malformed payload, and vt
falls back to an untracked spawn when the tracked spawn itself fails
(e.g. the preload library cannot be written to a read-only temp dir).
Runs with escaped processes are reported as not cached, never cached
from a partial trace; declaring explicit input/output config (without
auto) still caches in such environments.
Fixes#700.
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,6 @@
1
1
# Changelog
2
2
3
+
-**Fixed** Cached tasks no longer fail to spawn child processes in restricted sandboxes (e.g. rootless bubblewrap that denies the `seccomp` syscall). When file-access tracking cannot be set up for a process, the process runs untracked instead and the run is reported as not cached ([#700](https://github.com/voidzero-dev/vite-task/issues/700)).
3
4
-**Fixed**`vp run` no longer hangs or fails when a task leaves a process running behind it, such as a dev server or a background helper, or when one of a task's processes is killed. The run finishes as soon as the task itself does, and the files the task used are still recorded ([#544](https://github.com/voidzero-dev/vite-task/issues/544), [#675](https://github.com/voidzero-dev/vite-task/pull/675)).
4
5
-**Fixed** A task that reads or writes an unusually large number of files now runs to the end instead of being killed partway through. Vite+ reports the run as not cached, because it could not record every file the task used ([#533](https://github.com/voidzero-dev/vite-task/issues/533), [#675](https://github.com/voidzero-dev/vite-task/pull/675)).
5
6
-**Fixed** Vite+ diagnostics now display individual paths and working directories without Rust debug formatting such as quoted paths or escaped Windows backslashes ([#534](https://github.com/voidzero-dev/vite-task/pull/534)).
0 commit comments