-
Notifications
You must be signed in to change notification settings - Fork 256
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parallel gem installation with bundler can result in a pacman locking error #397
Comments
4 tasks
larskanis
added a commit
that referenced
this issue
Nov 21, 2024
pacman invocation must be serialized to avoid locking error. Fixes #397
larskanis
added a commit
that referenced
this issue
Nov 21, 2024
pacman invocation must be serialized to avoid locking error. Fixes #397
larskanis
added a commit
that referenced
this issue
Nov 21, 2024
pacman invocation must be serialized to avoid locking error. Fixes #397
larskanis
added a commit
that referenced
this issue
Nov 21, 2024
pacman invocation must be serialized to avoid locking error. Fixes #397
larskanis
added a commit
that referenced
this issue
Dec 30, 2024
pacman invocation must be serialized to avoid locking error. Fixes #397
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What problems are you experiencing?
With parallel gem installation per bundler can result in a pacman locking error. This can happen when installing multiple gems with
msys2_mingw_dependencies
metadata set. Parallel install is the default in all recent bundler versions.Steps to reproduce
With the following
Gemfile
and both mingw packages
libyaml
andopenssl
not yet installed, then thepacman
command is executed concurrently, resulting in a locking error:A second attempt succeeds, since only one package is missing now:
What's the output from
ridk version
?The text was updated successfully, but these errors were encountered: