lightning: fix panic when nextKey twice (#40959) #41074
Merged
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.
manually cherry-pick #40959
What problem does this PR solve?
Issue Number: close #40934
Problem Summary:
What is changed and how it works?
Avoid to let CommonHandle++ and decode it because the result may not be a valid value. The string datum encoding will not be ended with 0xff and we may increase 0xfe to 0xff.
tidb/util/codec/bytes.go
Lines 35 to 49 in 151cd7e
Check List
Tests
Run the changed tests and failpoints will trigger this panic. And after the fix it is avoided.
Side effects
Documentation
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.