chore(deps): update dependency pingcap/tiflash to v8.2.0

[renovate]

This PR contains the following updates:

Package	Update	Change
pingcap/tiflash	minor	v8.0.0 -> v8.2.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

pingcap/tiflash (pingcap/tiflash)

v8.2.0: TiFlash v8.2.0

Compare Source

For new features, improvements, and bug fixes released in 8.2.0 for tiflash, see TiDB 8.2.0 release notes.
See the difference from the issue perspective:

• #​7256
• #​8920
• #​8926
• #​8860
• #​8860
• #​8787
• #​8952
• #​8789
• #​8911
• #​8933
• #​8864
• #​8911
• #​8968
• #​8956
• #​8988
• #​8916
• #​8904
• #​9020
• #​8962
• #​9022
• #​9024
• #​8835
• #​9038
• #​9043
• #​9039
• #​9038
• #​8835
• #​9074
• #​9074
• #​9074
• #​8835
• #​8382
• #​9084
• #​9057
• #​9090
• #​9092
• #​9097
• #​8966
• #​8891
• #​9101
• #​9091
• #​8835
• #​9118
• #​9125
• #​8081
• #​9116
• #​8835
• #​9103
• #​9147
• #​8977
• #​8081
• #​8081
• #​7193
• #​8898
• #​9169

v8.1.0: TiFlash v8.1.0

Compare Source

For new features, improvements, and bug fixes released in 8.1.0 for tiflash, see TiDB 8.1.0 release notes.
See the difference from the issue perspective:

- pingcap/tiflash#8589, close pingcap/tiflash#8835

• #​8835

• #​8835

• #​8803

• #​8859

• #​8856

• #​8876

• #​7193, close #​8890

• #​8811

• #​8893, close #​8897

• #​8905

• #​8911

• #​8918

• #​8920

• #​8911

• #​8911, close #​8968

• #​8952

• #​8988

• #​8916

• #​8845

• #​9020

• #​9039

• #​8787

• #​8860

• #​8860

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: wuhuizuo

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 [wuhuizuo]

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

[codiumai-pr-agent-pro]

CI Failure Feedback 🧐

Action: build images with skaffold (builder-others-slow, linux/amd64, local-docker)

Failed stage: Build images [❌]

Failure summary: The action failed due to multiple issues encountered during the execution of the script: The repository centos-sclo-rh/x86_64 could not be resolved, leading to a failure in the yum package manager. Several commands were not found, including ninja, cmake, wget, make, and tar, indicating missing dependencies. Specific files required by the script, such as OpenSSL_1_1_1w.tar.gz, openssl-OpenSSL_1_1_1w, and install_ccache.sh, were not found. The script /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh and other related scripts failed due to missing commands and files.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 685: #7 9.066 centos-release-scl.noarch 0:2-3.el7.centos epel-release.noarch 0:7-11 686: #7 9.066 687: #7 9.066 Dependency Installed: 688: #7 9.066 centos-release-scl-rh.noarch 0:2-3.el7.centos 689: #7 9.066 690: #7 9.067 Complete! 691: #7 9.187 Loaded plugins: fastestmirror, ovl 692: #7 9.234 Loading mirror speeds from cached hostfile 693: #7 9.488 Could not retrieve mirrorlist http://mirrorlist.centos.org?arch=x86_64&release=7&repo=sclo-rh error was 694: #7 9.488 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" 695: #7 9.491 696: #7 9.491 697: #7 9.491 One of the configured repositories failed (Unknown), 698: #7 9.491 and yum doesn't have enough cached data to continue. At this point the only 699: #7 9.491 safe thing yum can do is fail. There are a few ways to work "fix" this: ... 711: #7 9.491 4. Disable the repository permanently, so yum won't use it by default. Yum 712: #7 9.491 will then just ignore the repository until you permanently enable it 713: #7 9.491 again or use --enablerepo for temporary usage: 714: #7 9.491 715: #7 9.491 yum-config-manager --disable <repoid> 716: #7 9.491 or 717: #7 9.491 subscription-manager repos --disable=<repoid> 718: #7 9.491 719: #7 9.491 5. Configure the failing repository to be skipped, if it is unavailable. 720: #7 9.491 Note that yum will try to contact the repo. when it runs most commands, 721: #7 9.491 so will have to try and fail each time (and thus. yum will be be much 722: #7 9.491 slower). If it is a very temporary problem though, this is often a nice 723: #7 9.491 compromise: 724: #7 9.491 725: #7 9.491 yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true 726: #7 9.491 727: #7 9.491 Cannot find a valid baseurl for repo: centos-sclo-rh/x86_64 728: #7 9.597 Loaded plugins: fastestmirror, ovl 729: #7 9.645 Loading mirror speeds from cached hostfile 730: #7 9.770 Could not retrieve mirrorlist http://mirrorlist.centos.org?arch=x86_64&release=7&repo=sclo-rh error was 731: #7 9.770 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" 732: #7 9.772 733: #7 9.772 734: #7 9.772 One of the configured repositories failed (Unknown), 735: #7 9.772 and yum doesn't have enough cached data to continue. At this point the only 736: #7 9.772 safe thing yum can do is fail. There are a few ways to work "fix" this: ... 748: #7 9.772 4. Disable the repository permanently, so yum won't use it by default. Yum 749: #7 9.772 will then just ignore the repository until you permanently enable it 750: #7 9.772 again or use --enablerepo for temporary usage: 751: #7 9.772 752: #7 9.772 yum-config-manager --disable <repoid> 753: #7 9.772 or 754: #7 9.772 subscription-manager repos --disable=<repoid> 755: #7 9.772 756: #7 9.772 5. Configure the failing repository to be skipped, if it is unavailable. 757: #7 9.772 Note that yum will try to contact the repo. when it runs most commands, 758: #7 9.772 so will have to try and fail each time (and thus. yum will be be much 759: #7 9.772 slower). If it is a very temporary problem though, this is often a nice 760: #7 9.772 compromise: 761: #7 9.772 762: #7 9.772 yum-config-manager --save --setopt=<repoid>.skip_if_unavailable=true 763: #7 9.772 764: #7 9.772 Cannot find a valid baseurl for repo: centos-sclo-rh/x86_64 765: #7 9.882 Loaded plugins: fastestmirror, ovl 766: #7 9.928 Loading mirror speeds from cached hostfile 767: #7 10.05 Could not retrieve mirrorlist http://mirrorlist.centos.org?arch=x86_64&release=7&repo=sclo-rh error was 768: #7 10.05 14: curl#6 - "Could not resolve host: mirrorlist.centos.org; Unknown error" 769: #7 10.06 770: #7 10.06 771: #7 10.06 One of the configured repositories failed (Unknown), 772: #7 10.06 and yum doesn't have enough cached data to continue. At this point the only 773: #7 10.06 safe thing yum can do is fail. There are a few ways to work "fix" this: ... 785: #7 10.06 4. Disable the repository permanently, so yum won't use it by default. Yum 786: #7 10.06 will then just ignore the repository until you permanently enable it 787: #7 10.06 again or use --enablerepo for temporary usage: 788: #7 10.06 789: #7 10.06 yum-config-manager --disable <repoid> 790: #7 10.06 or 791: #7 10.06 subscription-manager repos --disable=<repoid> 792: #7 10.06 793: #7 10.06 5. Configure the failing repository to be skipped, if it is unavailable. 794: #7 10.06 Note that yum will try to contact the repo. when it runs most commands, 795: #7 10.06 so will have to try and fail each time (and thus. yum will be be much ... 810: #7 10.29 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh: line 38: ninja: command not found 811: #7 10.29 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh: line 39: ninja: command not found 812: #7 10.29 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh: line 46: cmake: command not found 813: #7 10.29 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh: line 62: ninja: command not found 814: #7 10.29 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/bootstrap_llvm.sh: line 63: ninja: command not found 815: #7 10.29 /usr/local/lib/x86_64-unknown-linux-gnu 816: #7 10.30 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_openssl.sh: line 21: wget: command not found 817: #7 10.31 tar: OpenSSL_1_1_1w.tar.gz: Cannot open: No such file or directory 818: #7 10.31 tar: Error is not recoverable: exiting now 819: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_openssl.sh: line 23: cd: openssl-OpenSSL_1_1_1w: No such file or directory 820: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_openssl.sh: line 26: ./config: No such file or directory 821: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_openssl.sh: line 34: make: command not found 822: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_openssl.sh: line 35: make: command not found 823: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_git.sh: line 21: wget: command not found 824: #7 10.31 tar (child): ../git.tar.gz: Cannot open: No such file or directory 825: #7 10.31 tar (child): Error is not recoverable: exiting now 826: #7 10.31 tar: Child returned status 2 827: #7 10.31 tar: Error is not recoverable: exiting now 828: #7 10.31 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_git.sh: line 24: make: command not found 829: #7 10.32 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_git.sh: line 25: ./configure: No such file or directory 830: #7 10.32 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_git.sh: line 26: make: command not found 831: #7 10.32 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_git.sh: line 27: make: command not found 832: #7 10.32 /tiflash-release-8.2/release-centos7-llvm/dockerfiles/misc/install_go.sh: line 23: wget: command not found 833: #7 10.32 tar (child): go1.20.linux-amd64.tar.gz: Cannot open: No such file or directory 834: #7 10.32 tar (child): Error is not recoverable: exiting now 835: #7 10.32 tar: Child returned status 2 836: #7 10.32 tar: Error is not recoverable: exiting now ... 861: #7 18.47 the corresponding env file under $HOME/.cargo. 862: #7 18.47 863: #7 18.47 This is usually done by running one of the following (note the leading DOT): 864: #7 18.47 . "$HOME/.cargo/env" # For sh/bash/zsh/ash/dash/pdksh 865: #7 18.47 source "$HOME/.cargo/env.fish" # For fish 866: #7 18.49 cp: cannot stat '/tiflash-release-8.2/release-centos7-llvm/dockerfiles/cargo-config': No such file or directory 867: #7 18.49 ./bake_llvm_base_amd64.sh: line 61: /tiflash-release-8.2/release-centos7-llvm/dockerfiles/install_ccache.sh: No such file or directory 868: #7 18.49 ./bake_llvm_base_amd64.sh: line 62: install_ccache: command not found 869: #7 ERROR: process "/bin/sh -c FILE=$([ \"$(arch)\" = \"aarch64\" ] && echo \"bake_llvm_base_aarch64.sh\" || echo \"bake_llvm_base_amd64.sh\"); TAR_DIR=\"tiflash-release-$TIFLASH_VER\"; curl -sSL https://github.com/pingcap/tiflash/archive/refs/heads/release-${TIFLASH_VER}.tar.gz -o tiflash.tar.gz && tar -zxf tiflash.tar.gz \"$TAR_DIR/release-centos7-llvm/dockerfiles/misc\" && pushd \"$TAR_DIR/release-centos7-llvm/dockerfiles/misc\" && chmod +x * && ./${FILE} && popd && rm -rf tiflash.tar.gz \"$TAR_DIR\"" did not complete successfully: exit code: 127 ... 888: 23 | >>> curl -sSL https://github.com/pingcap/tiflash/archive/refs/heads/release-${TIFLASH_VER}.tar.gz -o tiflash.tar.gz && \ 889: 24 | >>> tar -zxf tiflash.tar.gz "$TAR_DIR/release-centos7-llvm/dockerfiles/misc" && \ 890: 25 | >>> pushd "$TAR_DIR/release-centos7-llvm/dockerfiles/misc" && \ 891: 26 | >>> chmod +x * && ./${FILE} && \ 892: 27 | >>> popd && \ 893: 28 | >>> rm -rf tiflash.tar.gz "$TAR_DIR" 894: 29 | 895: -------------------- 896: ERROR: failed to solve: process "/bin/sh -c FILE=$([ \"$(arch)\" = \"aarch64\" ] && echo \"bake_llvm_base_aarch64.sh\" || echo \"bake_llvm_base_amd64.sh\"); TAR_DIR=\"tiflash-release-$TIFLASH_VER\"; curl -sSL https://github.com/pingcap/tiflash/archive/refs/heads/release-${TIFLASH_VER}.tar.gz -o tiflash.tar.gz && tar -zxf tiflash.tar.gz \"$TAR_DIR/release-centos7-llvm/dockerfiles/misc\" && pushd \"$TAR_DIR/release-centos7-llvm/dockerfiles/misc\" && chmod +x * && ./${FILE} && popd && rm -rf tiflash.tar.gz \"$TAR_DIR\"" did not complete successfully: exit code: 127 897: exit status 1. Docker build ran into internal error. Please retry. 898: If this keeps happening, please open an issue.. 899: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-07-05 11:16:42.850574172 +0000 UTC m=+10700.085808278: ☑️ agreed by wuhuizuo.
• 2024-07-26 07:15:58.439881598 +0000 UTC m=+1202180.430823065: ✖️🔁 reset by renovate[bot].

[ti-chi-bot]

New changes are detected. LGTM label has been removed.