Add In-Memory Locking #179
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This pull request introduces a new in-memory lock utility to the codebase, providing a mechanism for safely executing code while ensuring mutual exclusion on named resources. It also adds a custom exception for lock acquisition timeouts.
Concurrency control:
Lockclass insrc/Objects/Support/Lock.phpthat provides static methods to acquire, release, and check named locks, as well as ablockmethod to execute callbacks while holding a lock. This helps prevent race conditions when accessing shared resources.Error handling:
LockTimeoutExceptioninsrc/Exceptions/LockTimeoutException.phpto be thrown when a lock cannot be acquired within the specified timeout period, improving error reporting and debugging for lock-related issues.