Skip to content

Conversation

ti-chi-bot
Copy link
Member

This is an automated cherry-pick of #61868

What problem does this PR solve?

Issue Number: close #60926

Problem Summary:

What changed and how does it work?

We introduce a new function CallWithRecover to recover the panic in the close of hash join v1

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.

Fix the issue that the panic in the close of hash join v1 is not recovered

@ti-chi-bot ti-chi-bot added do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/planner SIG: Planner 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 Jul 10, 2025
@ti-chi-bot
Copy link
Member Author

@xzhangxian1008 This PR has conflicts, I have hold it.
Please resolve them or ask others to resolve them, then comment /unhold to remove the hold label.

@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 Jul 10, 2025
@xzhangxian1008
Copy link
Contributor

/retest

1 similar comment
@xzhangxian1008
Copy link
Contributor

/retest

@xzhangxian1008
Copy link
Contributor

/retest

Copy link

codecov bot commented Jul 15, 2025

Codecov Report

Attention: Patch coverage is 54.54545% with 5 lines in your changes missing coverage. Please review.

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

Additional details and impacted files
@@               Coverage Diff                @@
##             release-8.1     #62341   +/-   ##
================================================
  Coverage               ?   71.3134%           
================================================
  Files                  ?       1469           
  Lines                  ?     425488           
  Branches               ?          0           
================================================
  Hits                   ?     303430           
  Misses                 ?     101510           
  Partials               ?      20548           
Flag Coverage Δ
unit 71.3134% <54.5454%> (?)

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

Components Coverage Δ
dumpling 52.9656% <0.0000%> (?)
parser ∅ <0.0000%> (?)
br 41.7485% <0.0000%> (?)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Jul 15, 2025
Copy link
Contributor

@windtalker windtalker left a comment

Choose a reason for hiding this comment

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

lgtm

Copy link

ti-chi-bot bot commented Jul 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: windtalker, xzhangxian1008

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 approved lgtm and removed needs-1-more-lgtm Indicates a PR needs 1 more LGTM. labels Jul 16, 2025
Copy link

ti-chi-bot bot commented Jul 16, 2025

[LGTM Timeline notifier]

Timeline:

  • 2025-07-15 09:42:44.89081381 +0000 UTC m=+2597617.613992791: ☑️ agreed by xzhangxian1008.
  • 2025-07-16 02:07:28.443465087 +0000 UTC m=+2656701.166644067: ☑️ agreed by windtalker.

@xzhangxian1008
Copy link
Contributor

/unhold

@ti-chi-bot ti-chi-bot bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Jul 16, 2025
@ti-chi-bot ti-chi-bot bot merged commit 6a6df40 into pingcap:release-8.1 Jul 16, 2025
18 checks passed
@xzhangxian1008 xzhangxian1008 deleted the cherry-pick-61868-to-release-8.1 branch July 16, 2025 07:48
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 ok-to-test Indicates a PR is ready to be tested. release-note Denotes a PR that will be considered when it comes time to generate release notes. sig/planner SIG: Planner 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.

3 participants