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

scheduler(ticdc): fix span loss bug when split regions (#11715) #11723

Merged

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #11715

What problem does this PR solve?

Issue Number: close #11675

What is changed and how it works?

Some regions may not append to spans because of incorrect condition judgment of restSpans.
Make sure all regions are added to the spans before returning.

Check List

Tests

  • Unit test
  • Integration test

Questions

Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?

Release note

`None`.

@ti-chi-bot ti-chi-bot added 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. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR. labels Nov 6, 2024
Copy link
Contributor

ti-chi-bot bot commented Nov 6, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wk989898

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 the approved label Nov 6, 2024
Copy link

codecov bot commented Nov 6, 2024

Codecov Report

Attention: Patch coverage is 17.24138% with 24 lines in your changes missing coverage. Please review.

Please upload report for BASE (release-8.1@8832898). Learn more about missing BASE report.

Additional details and impacted files
Components Coverage Δ
cdc 61.7876% <0.0000%> (?)
dm 51.0419% <0.0000%> (?)
engine 63.4161% <0.0000%> (?)
Flag Coverage Δ
unit 57.4040% <17.2413%> (?)

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

@@               Coverage Diff                @@
##             release-8.1     #11723   +/-   ##
================================================
  Coverage               ?   57.4040%           
================================================
  Files                  ?        854           
  Lines                  ?     126059           
  Branches               ?          0           
================================================
  Hits                   ?      72363           
  Misses                 ?      48289           
  Partials               ?       5407           

@ti-chi-bot ti-chi-bot bot added cherry-pick-approved Cherry pick PR approved by release team. and removed do-not-merge/cherry-pick-not-approved labels Nov 6, 2024
@wk989898
Copy link
Collaborator

wk989898 commented Nov 6, 2024

/retest

2 similar comments
@wk989898
Copy link
Collaborator

wk989898 commented Nov 6, 2024

/retest

@wk989898
Copy link
Collaborator

wk989898 commented Nov 6, 2024

/retest

@ti-chi-bot ti-chi-bot bot merged commit 0c49d2a into pingcap:release-8.1 Nov 6, 2024
27 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved cherry-pick-approved Cherry pick PR approved by release team. 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. type/cherry-pick-for-release-8.1 This PR is cherry-picked to release-8.1 from a source PR.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants