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

table: fix some txn assertion error when executing DDL and DML #55314

Merged
merged 1 commit into from
Aug 9, 2024

Conversation

lcwangchao
Copy link
Collaborator

@lcwangchao lcwangchao commented Aug 8, 2024

What problem does this PR solve?

Issue Number: close #55313

Problem Summary:

opt.IgnoreAssertion is corrupted if AddRecord has multiple indexes and one index is not in public state.

opt.IgnoreAssertion = opt.IgnoreAssertion || c.idxInfo.State != model.StatePublic

What changed and how does it work?

We should not change the value opt.IgnoreAssertion.

TODO: we should make all options immutable to avoid similar bugs.

Check List

Tests

  • Unit test
  • Integration test
  • Manual test (add detailed scripts or steps below)
  • No need to test
    • I checked and no code files have been changed.

Side effects

  • Performance regression: Consumes more CPU
  • Performance regression: Consumes more Memory
  • Breaking backward compatibility

Documentation

  • Affects user behaviors
  • Contains syntax changes
  • Contains variable changes
  • Contains experimental features
  • Changes MySQL compatibility

Release note

Please refer to Release Notes Language Style Guide to write a quality release note.

None

@ti-chi-bot ti-chi-bot bot added release-note-none Denotes a PR that doesn't merit a release note. do-not-merge/needs-triage-completed do-not-merge/needs-linked-issue size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 8, 2024
Copy link

tiprow bot commented Aug 8, 2024

Hi @lcwangchao. Thanks for your PR.

PRs from untrusted users cannot be marked as trusted with /ok-to-test in this repo meaning untrusted PR authors can never trigger tests themselves. Collaborators can still trigger tests on the PR using /test all.

I understand the commands that are listed here.

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.

Copy link

codecov bot commented Aug 8, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 74.7558%. Comparing base (d4c26ca) to head (b734806).
Report is 5 commits behind head on master.

Additional details and impacted files
@@               Coverage Diff                @@
##             master     #55314        +/-   ##
================================================
+ Coverage   74.7052%   74.7558%   +0.0506%     
================================================
  Files          1570       1570                
  Lines        364747     440977     +76230     
================================================
+ Hits         272485     329656     +57171     
- Misses        72490      91106     +18616     
- Partials      19772      20215       +443     
Flag Coverage Δ
integration 49.1474% <100.0000%> (?)
unit 71.7805% <100.0000%> (-1.8497%) ⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
dumpling 52.9567% <ø> (-2.2327%) ⬇️
parser ∅ <ø> (∅)
br 52.5421% <ø> (+4.8879%) ⬆️

@ti-chi-bot ti-chi-bot bot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Aug 8, 2024
@lcwangchao lcwangchao force-pushed the fix_55125 branch 2 times, most recently from a4a0aea to 070ec27 Compare August 8, 2024 14:37
@lcwangchao
Copy link
Collaborator Author

/retest

Copy link

tiprow bot commented Aug 9, 2024

@lcwangchao: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

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.

@ti-chi-bot ti-chi-bot bot added approved needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Aug 9, 2024
Copy link

ti-chi-bot bot commented Aug 9, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cfzjywxk, crazycs520

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Aug 9, 2024
Copy link

ti-chi-bot bot commented Aug 9, 2024

[LGTM Timeline notifier]

Timeline:

  • 2024-08-09 02:44:05.161505269 +0000 UTC m=+579175.028604354: ☑️ agreed by cfzjywxk.
  • 2024-08-09 02:46:33.307266419 +0000 UTC m=+579323.174365507: ☑️ agreed by crazycs520.

@ti-chi-bot ti-chi-bot bot merged commit 829bd5b into pingcap:master Aug 9, 2024
23 checks passed
@lcwangchao lcwangchao deleted the fix_55125 branch August 9, 2024 03:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved lgtm release-note-none Denotes a PR that doesn't merit a release note. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

unexpected assertion failed during replace/insert into statement
3 participants