-
Notifications
You must be signed in to change notification settings - Fork 27
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
Concurrent zkg create
operations can race on update of default package source
#139
Comments
When executing `zkg` concurrently multiple updates to the sources can race and destroy each others state. Disable that update. This is a workaround for zeek/package-manager#139.
The
|
I hit another one that is seemingly independent of the default source, but same class of errors, Cloning/checking out the template repo seems also racy:
|
zkg list seems to trigger the two you showed as well:
|
When executing `zkg` concurrently multiple updates to the sources can race and destroy each others state. Disable that update. This is a workaround for zeek/package-manager#139.
When executing `zkg` concurrently multiple updates to the sources can race and destroy each others state. Disable that update. This is a workaround for zeek/package-manager#139.
Yeah I think this is just not at all part of the model atm, and clearly should be. There's also the fact that ...
... covers surprisingly few operations because virtually everything starts with |
While working on zeek/package-template#4 I noticed that multiple concurrent
zkg create
operations can race on update of the default package source. I did not check which other operations can trigger such an update.I would have expected that an operation which does not obviously mutate zkg state does properly protect that state, e.g., with file locks.
Example:
As a workaround for my use case I am using a zkg config file with an empty
sources
section.The text was updated successfully, but these errors were encountered: