util: try to fix panic #61
Merged
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
djshow832
reviewed
Aug 30, 2022
djshow832
reviewed
Aug 30, 2022
Signed-off-by: xhe <xw897002528@gmail.com>
Signed-off-by: xhe <xw897002528@gmail.com>
djshow832
reviewed
Aug 31, 2022
pkg/util/cmd/encoder.go
Outdated
| return &tidbEncoder{c.EncoderConfig, 0, _pool.Get()} | ||
| } | ||
|
|
||
| func (c tidbEncoder) Clone() zapcore.Encoder { | ||
| return c.Clone() |
There was a problem hiding this comment.
Suggested change
| return c.Clone() | |
| return c.clone() |
Are you sure it calls itself?
There was a problem hiding this comment.
I should have changed this to c.clone(). Maybe I made mistakes in pull --rebase.
Co-authored-by: djshow832 <zhangming@pingcap.com>
djshow832
approved these changes
Sep 1, 2022
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.
What problem does this PR solve?
Issue Number: close None
Problem Summary: I don't know how it is produced.
len(xx) >= 0is expected, thus the judgement should be true forever. Anyway, this is a try.What is changed and how it works:
EncodeEntrywill not free the buffer anymore, it is left to zap logger, based on https://github.com/uber-go/zap/blob/4a895a245ab794e3ae965783843a9fbc793083bc/zapcore/core.go#L95-L100StackTraceby zap is multiline, this is not compatible withtidbformat.Check List
Tests
Notable changes
Release note
Please refer to Release Notes Language Style Guide to write a quality release note.