Skip to content

fix(foundryup): abort bootstrap on signals - #16818

Open
kriss39 wants to merge 1 commit into
foundry-rs:masterfrom
kriss39:fix/foundryup-signal-cancellation
Open

kriss39 wants to merge 1 commit into
foundry-rs:masterfrom
kriss39:fix/foundryup-signal-cancellation

Conversation

@kriss39

@kriss39 kriss39 commented Sep 11, 2026

Copy link
Copy Markdown

The foundryup bootstrap currently uses the same cleanup trap for EXIT, SIGINT, and SIGTERM. Because the cleanup handler returns successfully, cancelling the bootstrap can clean up the temp files and then continue running instead of stopping.

This changes signal handling so SIGINT exits with 130 and SIGTERM exits with 143, while the EXIT trap still handles cleanup. That keeps the existing launcher untouched when the bootstrap is interrupted.

I also added regression tests for both signals to make sure the bootstrap exits with the expected status, does not replace the launcher, and does not reach the final exec.

This was introduced as part of the Rust foundryup migration in #15498.

@github-actions

Copy link
Copy Markdown
Contributor

✅ Changelog found

The deterministic check will validate the changed entry.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: No status

Development

Successfully merging this pull request may close these issues.

1 participant