fix(forge): monitor beam rewriting worker process#370
Merged
doorgan merged 1 commit intoJun 24, 2026
Conversation
This was referenced Feb 10, 2026
QuinnWilton
changed the title
QuinnWilton
force-pushed
the
fix/forge-beams-unlinked-spawn
branch
from
972329d to
eb80bc2
Compare
Replace bare spawn with spawn_monitor in Beams.apply_to_all/2.
If the worker process crashed, the parent would hang forever
waiting for :progress messages that would never arrive.
Propagate the monitor ref through block_until_done and raise on
{:DOWN, ...} so crashes surface immediately. Demonitor on normal
completion.
doorgan
force-pushed
the
fix/forge-beams-unlinked-spawn
branch
from
eb80bc2 to
b81abb3
Compare
doorgan
approved these changes
Jun 24, 2026
|
Successfully created backport PR for |
expert-backports Bot
added a commit
that referenced
this pull request
Jun 24, 2026
# Description Backport of #370 to `v0.1`. Co-authored-by: Quinn Wilton <quinn@quinnwilton.com>
doorgan
pushed a commit
that referenced
this pull request
Jun 24, 2026
This is part of a set of 4 PRs that arose out of some static analysis tooling I'm working on: - #369 - #370 - #371 - #372 That means that these aren't crashes or issues that I've observed in practice, however based on my reading of the code, they do represent issues worth addressing. ## Problem: This is effectively the same issue as in #370, where the use of a bare `spawn/2` causes the spawning process to hang indefinitely while waiting for a message from the spawned process, and preventing `Credo` diagnostics from being updated. ## Solution Replace `spawn/1` with `spawn_monitor/1`, and add a `receive` clause to handle the spawned process unexpectedly terminating before sending a result. In the successful case, the monitor is flushed to avoid `:DOWN` messages building up and causing a mailbox leak. A 30 second timeout is also added, to prevent buggy or broken `Credo` modules from causing the entire system to hang.
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
3 participants
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.
This is part of a set of 4 PRs that arose out of some static analysis tooling I'm working on:
That means that these aren't crashes or issues that I've observed in practice, however based on my reading of the code, they do represent issues worth addressing.
Problem:
Beams.apply_to_all/2spawns its worker process using a barespawn/1, and then blocks inblock_until_done/3until it receives a:progressmessage from it. If the worker crashes, this message will never arrive, and the caller will block indefinitely.Solution
Replace
spawn/1withspawn_monitor/1, and add areceiveclause inblock_until_done/3to handle the worker unexpectedly terminating before a:progressmessage is sent, so that we're able to immediately raise instead of blocking forever.In the successful case, the monitor is flushed to avoid
:DOWNmessages building up and causing a mailbox leak.