Acquire rewatch build lock before initialization#8409
Merged
Conversation
Member
Author
|
@codex review |
|
Codex Review: Didn't find any major issues. 🎉 ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. Codex can also answer questions or update the PR. Try commenting "@codex address that feedback". |
jfrolich
approved these changes
May 4, 2026
rescript
@rescript/darwin-arm64
@rescript/darwin-x64
@rescript/linux-arm64
@rescript/linux-x64
@rescript/runtime
@rescript/win32-x64
commit: |
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
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
build.lockis meant to prevent multiplerewatch buildprocesses from mutating the same project build artifacts at the same time.Before this change,
build::buildcalledinitialize_buildbefore acquiringbuild.lock. That was unsafe because initialization is not read-only: it reads the previous compile state and callscleanup_previous_build, which can remove stale.ast,.iast,.cmi,.cmj,.cmt,.cmti, and generated JS artifacts underlib/bs.If two
rewatch buildprocesses started at the same time in the same project, both could enter initialization and cleanup concurrently. Only later, when each reachedincremental_build, would one process wait onbuild.lock. By then, both processes may already have inspected or mutated the previous build state, which can lead to racey cleanup and nondeterministic dirty-module state.Summary
build.lockbeforebuild::buildruns initialization.build.ninjawrites.incremental_buildkeeps its existing public locking behavior while full builds can use a wider lock boundary.build::buildwaits for an existingbuild.lockbefore initialization starts.