dm: failed to track table schema for online ddl when use binlog skip

[GMHDBJD]

What did you do?

binlog skip a online ddl

What did you expect to see?

skip successfully and track upstream schema

What did you see instead?

[2023/08/15 18:15:59.610 +08:00] [WARN] [syncer.go:2202] ["failed to track query when handle-error skip"] [task=test] [unit="binlog replication"] [error="[code=44007:class=schema-tracker:scope=downstream:level=medium], Message: cannot fetch downstream table schema of `shardddl`.`_tb1_new` to initialize upstream schema `shardddl1`.`_tb1_new` in schema tracker, RawCause: Error 1146 (42S02): Table 'shardddl._tb1_new' doesn't exist"] 

Versions of the cluster

DM version (run dmctl -V or dm-worker -V or dm-master -V):

(paste DM version here, and you must ensure versions of dmctl, DM-worker and DM-master are same)

Upstream MySQL/MariaDB server version:

(paste upstream MySQL/MariaDB server version here)

Downstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):

(paste TiDB cluster version here)

How did you deploy DM: tiup or manually?

(leave TiUP or manually here)

Other interesting information (system version, hardware config, etc):

>
>

current status of DM cluster (execute query-status <task-name> in dmctl)

(paste current status of DM cluster here)