util: fix a encode bug causes the wrong result of ... (#18855) #18859
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
Signed-off-by: ti-srebot <[email protected]>
|
/run-all-tests |
ti-srebot
added
component/expression
priority/release-blocker
ti-srebot
added
status/LGT2
zz-jason
added
the
status/can-merge
|
/run-all-tests |
|
@ti-srebot merge failed. |
zz-jason
changed the title
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 #18855 to release-4.0
Signed-off-by: wjhuang2016 [email protected]
What problem does this PR solve?
Issue Number: close #18850
Problem Summary:
Previously, we use the offset of set or enum to decide if two sets or enum are equal, which is not always correct.
What is changed and how it works?
What's Changed:
When encode set or enum, use the offset to get the original string
Related changes
Check List
Tests
Side effects
Release note