fix: remove --experimental_guard_against_concurrent_changes from recommended correctness settings #380
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.
We have observed that this settings leads to WARNINGS in npm package directory artifacts in the symlinked node_modules output tree created by rules_js for some npm packages.
For example,
When this happens, it appears to make all downstream actions of that tree artifact the WARNING is for be cache misses.
Possibly related to bazelbuild/bazel#5566