expression: fix wrong behavior in values function for Bit(1). (#15350) #15487
Conversation
This file contains 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
|
/run-all-tests |
sre-bot
added
component/expression
type/3.1-cherry-pick
type/bug-fix
wshwsh12
force-pushed
the
release-3.1-1bd1c07c05af
branch
from
9416c06
to
2eb589d
Compare
qw4990
added
status/LGT2
SunRunAway
added
the
status/can-merge
|
Your auto merge job has been accepted, waiting for 15203 |
|
/run-all-tests |
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.
cherry-pick #15350 to release-3.1
What problem does this PR solve?
Fixes #15310
What is changed and how it works?
Check the data length in built-in function ValuesInt().
Check List
Tests
Code changes
Side effects
Related changes
Release note
Fix wrong behavior in values function for type bit(n).