Skip to content
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

fix: check lock result in run mutexed fn #30

Merged
merged 3 commits into from
Aug 3, 2023

Conversation

monkeyDluffy6017
Copy link

wraps resty.lock:lock() with pcall, but it was only checking the pcall return status and not the actual result of the lock operation. Therefore it would continue even if no lock was acquired.

wraps resty.lock:lock() with pcall, but it was only checking the pcall
return status and not the actual result of the lock operation. Therefore
it would continue even if no lock was acquired.
@monkeyDluffy6017 monkeyDluffy6017 merged commit 617cbd2 into master Aug 3, 2023
monkeyDluffy6017 added a commit that referenced this pull request Aug 3, 2023
* This fixes a bug in the run_mutexed_fn function. The function
wraps resty.lock:lock() with pcall, but it was only checking the pcall
return status and not the actual result of the lock operation. Therefore
it would continue even if no lock was acquired.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants