pkg/errctx, *: use errctx to handle TruncateError

[YangKeao]

What problem does this PR solve?

Issue Number: close #48919

Problem Summary:

I tried to use errctx to handle the TruncateError in this PR. The comment in #48919 (comment) is useful for reading this PR.

What changed and how does it work?

1. Remove the flags related with TruncateError in types.Context, and also remove the function HandleTruncate.
2. Replace every HandleTruncate with HandleError.
3. Use HandleError to handle the errors if needed, after calling to the functions inside types.

The problem is that, we don't know when it's needed to call HandleError. Even the TruncateErr is not always handled inside types package (previously). Some of these errors will return without considering TruncateAsWarning... And the original logic depends on this behavior. It's impossible to tell or predict the "correct" behavior of the types package before this PR.

With this PR, I made the behavior of the functions in types clearer. These functions will always return a valid result even if an error is returned. For example, Compare float with string will fail if the string cannot be parsed as a float. Previously, Compare will always return 0 in this situation. Now, it will compare the float with the truncated value and give a result.

I'm not confident that the current behavior is 100% same with the original one, but at least it passed all test cases and we can have a clearer mind when we are handling errors/warnings in the future.

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.

Release note

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

None

[codecov]

Codecov Report

Attention: Patch coverage is 80.53571% with 109 lines in your changes missing coverage. Please review.

Project coverage is 72.5225%. Comparing base (ef02d72) to head (60c6173).
Report is 2231 commits behind head on master.

Additional details and impacted files

@@               Coverage Diff                @@
##             master     #48970        +/-   ##
================================================
+ Coverage   70.9932%   72.5225%   +1.5292%     
================================================
  Files          1368       1391        +23     
  Lines        403988     411180      +7192     
================================================
+ Hits         286804     298198     +11394     
+ Misses        97214      94175      -3039     
+ Partials      19970      18807      -1163     

Flag	Coverage Δ
integration	43.7192% <80.5357%> (?)
unit	70.9813% <ø> (-0.0119%)	⬇️

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

Components	Coverage Δ
dumpling	53.9663% <ø> (ø)
parser	∅ <ø> (∅)
br	48.3667% <0.0000%> (-4.6156%)	⬇️

[YangKeao]

/retest

[YangKeao]

/retest

[YangKeao]

/retest

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: lcwangchao
Once this PR has been reviewed and has the lgtm label, please assign benjamin2037, windtalker for approval. For more information see the Kubernetes Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS [lcwangchao]
• br/pkg/lightning/OWNERS
• pkg/ddl/OWNERS
• pkg/expression/OWNERS
• pkg/table/OWNERS
• pkg/tablecodec/OWNERS

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-11-30 07:33:23.808053628 +0000 UTC m=+1080832.473279827: ☑️ agreed by lcwangchao.

[ti-chi-bot]

PR needs rebase.

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.

[ti-chi-bot]

@YangKeao: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
idc-jenkins-ci-tidb/build	60c6173	link	true	/test build
idc-jenkins-ci-tidb/check_dev	60c6173	link	true	/test check-dev
idc-jenkins-ci-tidb/check_dev_2	60c6173	link	true	/test check-dev2
idc-jenkins-ci-tidb/mysql-test	60c6173	link	true	/test mysql-test
idc-jenkins-ci-tidb/unit-test	60c6173	link	true	/test unit-test
pull-integration-ddl-test	60c6173	link	true	/test pull-integration-ddl-test
pull-mysql-client-test	60c6173	link	true	/test pull-mysql-client-test
pull-br-integration-test	60c6173	link	true	/test pull-br-integration-test
pull-lightning-integration-test	60c6173	link	true	/test pull-lightning-integration-test

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.