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 empty result in getMaxThreadStatus for NDB_BVL_Feedback #3141

Merged
merged 1 commit into from
Oct 6, 2017

Conversation

driusan
Copy link
Collaborator

@driusan driusan commented Sep 11, 2017

The NDB_BVL_Feedback class incorrectly had a isset check instead of an !empty
check to determine if an SQL query returned any results. isset would never
be false, because the variable is set directly above the check.

This updates it to be !empty, so that "null" is properly returned when
there is no feedback.

The NDB_BVL_Feedback class incorrectly had a isset check instead of an !empty
check to determine if an SQL query returned any results. isset would never
be false, because the variable is set directly above the check.

This updates it to be !empty, so that "null" is properly returned when
there is no feedback.
@driusan driusan added the Category: Bug PR or issue that aims to report or fix a bug label Sep 11, 2017
@driusan driusan added this to the 17.2 milestone Sep 11, 2017
@driusan driusan removed this from the 18.1 milestone Oct 2, 2017
@driusan driusan changed the base branch from 17.1-dev to bugfix October 5, 2017 17:58
@kongtiaowang kongtiaowang added the Passed manual tests PR has been successfully tested by at least one peer label Oct 5, 2017
@kongtiaowang kongtiaowang self-requested a review October 5, 2017 19:42
Copy link
Contributor

@kongtiaowang kongtiaowang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@driusan driusan added this to the 18.0.1 milestone Oct 6, 2017
@driusan driusan merged commit 178d9be into aces:bugfix Oct 6, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Bug PR or issue that aims to report or fix a bug Passed manual tests PR has been successfully tested by at least one peer
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants