[6.x] Check if an array lock exists before releasing it - #31795
Merged
Conversation
Member
|
Thanks for fixing this for everyone Paul and, if I’m not mistaken, congrats on your first contribution to Laravel 🥳 |
Contributor
Author
|
Yeah, that's my first contribution. Thanks for helping me with it though! :) |
Member
|
No worries, always happy to help |
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
3 participants
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.
It just fixes the thing where we would be thrown an Undefined index {index} exception when releasing a non-existing array lock.
Reference: #30253 (comment)
Thanks to @timacdonald for adding the ArrayLock and the test for this PR!