@seiya-annie: The label(s) found/comminity cannot be applied, because the repository doesn't have them.
In response to [this](https://github.com/pingcap/tiflow/issues/11374#issuecomment-2210612095):
>/found comminity
Instructions for interacting with me using PR comments are available [here](https://prow.tidb.net/command-help). If you have questions or suggestions related to my behavior, please file an issue against the [ti-community-infra/tichi](https://github.com/ti-community-infra/tichi/issues/new?title=Prow%20issue:) repository.
What did you do?
As described in https://asktug.com/t/topic/1028447. Config as follows:
block-allow-list: bw-rule-1: do-dbs: [“next_"] ignore-tables:
Start task:![image](https://github.com/pingcap/tiflow/assets/9443637/0ff93d82-554b-4cc3-b0a9-b369a7c046dd)
What did you expect to see?
There are rules as below in ignore tables:
What did you see instead?
Check task details in WebUI![image](https://github.com/pingcap/tiflow/assets/9443637/9080e68a-1f70-4492-9b69-34df687bc53f)
Versions of the cluster
DM version (run
dmctl -V
ordm-worker -V
ordm-master -V
):Upstream MySQL/MariaDB server version:
Downstream TiDB cluster version (execute
SELECT tidb_version();
in a MySQL client):How did you deploy DM: tiup or manually?
Other interesting information (system version, hardware config, etc):
v8.1.0
current status of DM cluster (execute
query-status <task-name>
in dmctl)