li3zhi4 commented on PR #11746:
URL: https://github.com/apache/seatunnel/pull/11746#issuecomment-5990038035

   **`Dead links` \u2014 not caused by this PR.** The job reports exactly 2 
dead links, and both are in the repository-root `README.md`:\n\n```\n[\u2716] 
https://deepwiki.com/apache/seatunnel\n[\u2716] 
https://deepwiki.com/badge.svg\n```\n\nThey come from the DeepWiki badge on 
line 8 (`[![Ask 
DeepWiki](https://deepwiki.com/badge.svg)](https://deepwiki.com/apache/seatunnel)`),
 introduced upstream by `6de6f1b953` \"[Improve][Connector-V2][File] Optimize 
file discovery and update comparison for sync_mode=update (#11312)\". This PR 
touches no documentation at all \u2014 its diff is confined to `seatunnel-api`, 
`connector-cdc-base`, `seatunnel-engine-server`, the MySQL CDC e2e module and 
one `.conf` resource. So the failure is inherited from `dev` (the badge check 
depends on `deepwiki.com` being reachable from the runner, which is an 
external-network condition), not something the merge introduced.\n\nI re-ran 
the failed jobs on this branch; the same two `Dead links` links came back red. J
 ob log for the record: 
https://github.com/li3zhi4/seatunnel/actions/runs/36513175279/job/111637757509\n\nI'll
 keep an eye on the new head's run (`02a265f51`) and report the result here.\n


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to