fix(fspy): avoid static spawnSync failures#500
Draft
wan9chi wants to merge 1 commit into
Draft
Conversation
wan9chi
force-pushed
the
fix/issue-499-fspy-static-spawn
branch
from
d59101b to
11f634d
Compare
Co-authored-by: GPT-5 Codex <codex@openai.com>
wan9chi
force-pushed
the
fix/issue-499-fspy-static-spawn
branch
from
11f634d to
24e69fd
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Motivation
Fix #499. Cached
vp runtasks could make NodespawnSyncfail withEINVALwhen a dynamically linked task process spawned a statically linked Linux tool such astsgolint; fspy attempted seccomp-unotify instrumentation from theposix_spawnhook before the child existed. This lets the child spawn, marks fspy tracking incomplete, and skips writing a cache entry instead of failing the task.