nix: stop passing watchman socket to Nix builds #13784
Merged
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 passing of Watchman socket was implemented in order to avoid this:
Which is caused by
jest-haste-map
used bymetro
starting to watch the filesystem for file changes, which is pointless when doing a one-off build using Nix. But by settingCI=true
we can makemetro
not start this waching of files in the first place, removing the need for use of Watchman entirely.By entirely dropping use of Watchman we also fix the following issue:
Which happens on multi-user Nix installations becuase the user that the Nix build is executed as is not the same as the user that starts Watchman and creates the socket file.
Issue: #13783