You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should add a "lock" used by the package manager when mutations to the workspace are being made by the package manager – i.e. if a user happens to run two package manager operations that mutate the package at the same time, they should be serialized.
We can do this by using the standard UNIX file locking facilities (and things like writing the PID into the lockfile so that we be resilient to situations where we crashed with the lock held).
The text was updated successfully, but these errors were encountered:
Additional Detail from JIRA
md5: deebdabbf55390f322fa9aa68c43ed31
Issue Description:
We should add a "lock" used by the package manager when mutations to the workspace are being made by the package manager – i.e. if a user happens to run two package manager operations that mutate the package at the same time, they should be serialized.
We can do this by using the standard UNIX file locking facilities (and things like writing the PID into the lockfile so that we be resilient to situations where we crashed with the lock held).
The text was updated successfully, but these errors were encountered: