fix: auto-pin race condition on go.mod file #521
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.
When using
-toolexec
mode, the auto-pin process may be initiated by multiple concurrent executions of thetoolexec
proxy. In such cases, there is a race condition on access togo.mod
andorchestrion.tool.go
, which often results ingo mod tidy
failing due to it detecting concurrent modifications of thego.mod
(it may also result in corrupt content of theorchestrion.tool.go
file).This addresses the issue by having the auto-pin process acquire an advisory write lock on the
go.mod
file, making sure all attempts are properly synchronized, and only one attempt tries to modify the file at a time.Fixes #491