ddl,expression: introduce CtxWithHandleTruncateErrLevel to wrap a expression context to handle truncate error

[lcwangchao]

What problem does this PR solve?

Issue Number: ref #53388

What changed and how does it work?

This PR removes handleWithTruncateErr and then introduce CtxWithHandleTruncateErrLevel to make override truncate error handle in the context for some reasons:

• CtxWithHandleTruncateErrLevel creates a new context without modifying the old context. It is more safe in concurrency.
• CtxWithHandleTruncateErrLevel receives context.BuildContext as an input. So we can replace mock.Context with the NewStaticExprContext to make code strong.

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 @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.

[codecov]

Codecov Report

Attention: Patch coverage is 98.27586% with 1 lines in your changes are missing coverage. Please review.

Project coverage is 75.2855%. Comparing base (07508df) to head (0e3b35c).
Report is 37 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #53441        +/-   ##
================================================
+ Coverage   72.5282%   75.2855%   +2.7573%     
================================================
  Files          1505       1505                
  Lines        429845     429886        +41     
================================================
+ Hits         311759     323642     +11883     
+ Misses        98811      85953     -12858     
- Partials      19275      20291      +1016     

Flag	Coverage Δ
integration	50.4219% <86.2069%> (?)
unit	71.3422% <98.2758%> (-0.0809%)	⬇️

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

Components	Coverage Δ
dumpling	53.9957% <ø> (ø)
parser	∅ <ø> (∅)
br	60.4555% <ø> (+19.0685%)	⬆️

[lcwangchao]

/retest

[tiprow]

@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.

[zimulala]

LGTM

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-05-28 02:25:07.697317758 +0000 UTC m=+2743261.454453323: ☑️ agreed by zimulala.
• 2024-05-28 02:53:07.335415268 +0000 UTC m=+2744941.092550841: ☑️ agreed by hawkingrei.

[windtalker]

LGTM

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hawkingrei, windtalker, zimulala

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:

• pkg/ddl/OWNERS [zimulala]
• pkg/expression/OWNERS [windtalker]
• pkg/planner/OWNERS [hawkingrei]

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