Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

*: fix panic when check null rejection for from_unixtime #12413

Merged
merged 6 commits into from
Sep 30, 2019

Conversation

zz-jason
Copy link
Member

Signed-off-by: Zhang Jian zjsariel@gmail.com

What problem does this PR solve?

fix #12385

What is changed and how it works?

check whether the argument is NULL before using the value pointer.

Check List

Tests

  • Unit test
  • Integration test

Code changes

  • Has exported function/method change
  • Has exported variable/fields change

Related changes

  • Need to cherry-pick to the release branch

Release note

fix the panic when check null rejection for `from_unixtime`.

Signed-off-by: Zhang Jian <zjsariel@gmail.com>
Signed-off-by: Zhang Jian <zjsariel@gmail.com>
@codecov
Copy link

codecov bot commented Sep 26, 2019

Codecov Report

Merging #12413 into master will increase coverage by 0.7854%.
The diff coverage is n/a.

@@               Coverage Diff               @@
##             master    #12413        +/-   ##
===============================================
+ Coverage   79.8085%   80.594%   +0.7854%     
===============================================
  Files           460       460                
  Lines        102152    106328      +4176     
===============================================
+ Hits          81526     85694      +4168     
+ Misses        14739     14706        -33     
- Partials       5887      5928        +41

@zz-jason
Copy link
Member Author

/run-all-tests

Copy link
Contributor

@XuHuaiyu XuHuaiyu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@zz-jason zz-jason added needs-cherry-pick-2.1 status/LGT1 Indicates that a PR has LGTM 1. labels Sep 26, 2019
Copy link
Contributor

@qw4990 qw4990 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@qw4990 qw4990 added status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. and removed status/LGT1 Indicates that a PR has LGTM 1. labels Sep 30, 2019
@sre-bot
Copy link
Contributor

sre-bot commented Sep 30, 2019

/run-all-tests

@sre-bot
Copy link
Contributor

sre-bot commented Sep 30, 2019

/run-all-tests

@sre-bot sre-bot merged commit 01dce81 into pingcap:master Sep 30, 2019
@zz-jason zz-jason deleted the dev/fix-null-rejective branch September 30, 2019 03:11
@sre-bot
Copy link
Contributor

sre-bot commented Sep 30, 2019

cherry pick to release-2.1 failed

@sre-bot
Copy link
Contributor

sre-bot commented Sep 30, 2019

cherry pick to release-3.1 failed

@sre-bot
Copy link
Contributor

sre-bot commented Sep 30, 2019

cherry pick to release-3.0 failed

zz-jason added a commit to zz-jason/tidb that referenced this pull request Oct 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component/expression status/can-merge Indicates a PR has been approved by a committer. status/LGT2 Indicates that a PR has LGTM 2. type/bugfix This PR fixes a bug.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

tidb server panic
4 participants