UniPS: Catch exception when dumping incr snapshot

[CalvinNeo]

What problem does this PR solve?

Issue Number: close #9406, close #9098

Problem Summary:

1. Print error message and stack
2. Print error when GetObject timeout

What is changed and how it works?

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

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

None

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: JinheLin, Lloyd-Pottiger

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 [JinheLin,Lloyd-Pottiger]

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:

• 2024-09-04 07:48:48.743261317 +0000 UTC m=+430653.261314241: ☑️ agreed by JinheLin.
• 2024-09-04 08:46:58.852466659 +0000 UTC m=+434143.370519583: ☑️ agreed by Lloyd-Pottiger.

[CalvinNeo]

/retest

[JaySon-Huang]

nit change

Suggested change

	throw Exception(ErrorCodes::LOGICAL_ERROR, "fake checkpoint write exception");
	throw Exception(ErrorCodes::FAIL_POINT_ERROR, "fake checkpoint write exception");

[CalvinNeo]

It should be LOGICAL_ERROR. Because there is another error ErrorCodes::REGION_DATA_SCHEMA_UPDATED which could make prehandle to retry. So error codes matters here.

[purelind]

/retest

[JaySon-Huang]

/hold

[JaySon-Huang]

@CalvinNeo In summary:

1. operator * / operator-> is a more concise way to accessing an std::optional instance
2. When logging down the elapsed time in seconds, better use "{:.3f}" to format the output. The output of a floating number using "{}" is not readable sometime.
   here is an example: https://godbolt.org/z/qvrxT7q1Y

[CalvinNeo]

@CalvinNeo In summary:

1. operator * / operator-> is a more concise way to accessing an std::optional instance
2. When logging down the elapsed time in seconds, better use "{:.3f}" to format the output. The output of a floating number using "{}" is not readable sometime.
   here is an example: https://godbolt.org/z/qvrxT7q1Y

Got it

[CalvinNeo]

/unhold

[ti-chi-bot]

@CalvinNeo: Your PR was out of date, I have automatically updated it for you.

At the same time I will also trigger all tests for you:

/run-all-tests

trigger some heavy tests which will not run always when PR updated.

If the CI test fails, you just re-trigger the test that failed and the bot will merge the PR for you after the CI passes.

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 ti-community-infra/tichi repository.