session: allow end aborted txn via binary protocal

[zyguan]

What problem does this PR solve?

Issue Number: close #49151

Problem Summary: When a transaction has been aborted by TTL manager, we cannot commit/rollback it via binary protocal.

What changed and how does it work?

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

[tiprow]

Hi @zyguan. 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/test-infra repository.

[codecov]

Codecov Report

Merging #49384 (c1d4023) into master (965ad8a) will decrease coverage by 0.4791%.
The diff coverage is 0.0000%.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #49384        +/-   ##
================================================
- Coverage   71.9292%   71.4501%   -0.4791%     
================================================
  Files          1438       1434         -4     
  Lines        345726     436734     +91008     
================================================
+ Hits         248678     312047     +63369     
- Misses        76799     105560     +28761     
+ Partials      20249      19127      -1122     

Flag	Coverage Δ
integration	43.8733% <0.0000%> (?)
unit	71.1136% <ø> (-0.8156%)	⬇️

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

Components	Coverage Δ
dumpling	53.9663% <ø> (-2.3466%)	⬇️
parser	∅ <ø> (∅)
br	46.7815% <ø> (-4.8454%)	⬇️

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

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

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:

• OWNERS [crazycs520,ekexium]

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]

[LGTM Timeline notifier]

Timeline:

• 2023-12-20 04:24:48.93022913 +0000 UTC m=+1021379.967456059: ☑️ agreed by ekexium.
• 2024-01-02 08:05:14.213115077 +0000 UTC m=+2157805.250342006: ☑️ agreed by crazycs520.

[zyguan]

/retest-required

[tiprow]

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

In response to this:

/retest-required

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/test-infra repository.

[zyguan]

/ok-to-test

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.1: #50003.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-6.5: #50004.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.1: #50005.

[ti-chi-bot]

In response to a cherrypick label: new pull request created to branch release-7.5: #50006.