-
Notifications
You must be signed in to change notification settings - Fork 243
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
Resource locking serializes concurrent buf executions? #2863
Comments
It's possible - for example, depending on what is in |
@bufdev It's all local: cat fooRequest.json | buf convert ./my_proto_project --type="com.mycompany.FooRequest" --from -#format=json --to -#format=binpb |
We need something that we can run locally. If you can set up, for example, a temporary github repostory with the code you are executing, so that we can run this code and reproduce the issue, we're happy to look into it! |
No problem. I'll get to that soon! |
Closing since we can't reproduce, but if you can provide us a reproducible example, we're happy to look into it! |
Hello all,
It seems to me like
buf convert
(and maybe other commands) locks on some resource. If so, could this be either changed, documented or worked around on my side?For example, in a hacky script to process a bunch of files I tried:
As you can see on the fourth line, I spawn processes in the background to try and speed things up. However, the result was the same as when I did not spawn them in the background. So, it seemed to me that the
buf convert
processes are queueing up and waiting for some resource.The text was updated successfully, but these errors were encountered: