store/helper: use hex encoding for region key in log#65560
store/helper: use hex encoding for region key in log#65560ti-chi-bot[bot] merged 2 commits intopingcap:masterfrom
Conversation
|
Hi @MkDev11. Thanks for your PR. I'm waiting for a pingcap member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
Welcome @MkDev11! |
|
/ok-to-test |
|
@MkDev11: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
1 similar comment
|
@MkDev11: Cannot trigger testing until a trusted user reviews the PR and leaves an DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/assign @sylzd |
|
/ok-to-test |
|
/assign @lance6716 |
|
@lance6716 could you please approve this small PR? :) |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #65560 +/- ##
================================================
- Coverage 77.7946% 77.6032% -0.1914%
================================================
Files 1992 1916 -76
Lines 544075 531755 -12320
================================================
- Hits 423261 412659 -10602
+ Misses 119155 119088 -67
+ Partials 1659 8 -1651
Flags with carried forward coverage won't be shown. Click here to find out more.
🚀 New features to boost your workflow:
|
|
@YangKeao thanks for your quick approval. Could you please merge it now? |
|
/retest |
|
@YangKeao @lance6716 That failing check is not related to the PR. Please let me know if you can merge it. |
|
/retest |
|
merging is automatically done by bot. we can only retry flaky tests. |
|
Thanks for your reply! |
|
/retest-required |
|
@lance6716 could you please let me know why bot doesn't merge my PR yet? |
|
/hold |
cb687c9 to
b1e641c
Compare
b1e641c to
1ff91ae
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: lance6716, tangenta, YangKeao The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest-required |
1ff91ae to
406b339
Compare
Use hex.EncodeToString instead of zap.ByteString to display region keys in logs. zap.ByteString assumes valid UTF-8 and replaces invalid bytes with Unicode replacement characters, making the output unhelpful for debugging binary keys. Close pingcap#65357
406b339 to
4aff1a9
Compare
|
/retest |
1 similar comment
|
/retest |
|
all checks passed! |
What problem does this PR solve?
Issue Number: ref #65357
Problem Summary: When logging a failed region key decode in
NewFrameItemFromRegionKey,zap.ByteStringis used which assumes valid UTF-8. Non-UTF8 binary keys get displayed with Unicode replacement characters (\uFFFD), making logs unhelpful for debugging.What changed and how does it work?
Use
hex.EncodeToStringinstead ofzap.ByteStringto display the region key in hex format, which properly represents all binary data.Check List
Tests
Side effects
Documentation
Release note