zhangshenghang opened a new pull request, #12830: URL: https://github.com/apache/seatunnel/pull/12830
## Purpose of this PR The **Ask DeepWiki** badge in the README currently renders as a broken image. **Root cause:** the badge image `https://deepwiki.com/badge.svg` currently returns **HTTP 429** with a *Vercel Security Checkpoint* challenge page for all non-interactive (server-side) clients. GitHub renders README images through its camo image proxy, which fetches server-side, so it receives the 429 HTML page instead of the SVG and the badge shows as broken. The README markup itself follows DeepWiki's official recommended badge syntax — the issue is purely on the image host side, and it affects every repository hot-linking this badge. ## What changes - Add the badge SVG to the repository at `docs/images/deepwiki-badge.svg` (identical content to the official badge, same as what a browser receives after passing the challenge). - Point the README badge at the relative path `docs/images/deepwiki-badge.svg`, consistent with the existing README usage of relative image paths (e.g. `docs/images/architecture_diagram.png`). The link target remains https://deepwiki.com/apache/seatunnel. This makes the badge rendering independent of third-party service availability. ## How is this PR tested? - Rendered the README locally with the relative path: badge displays correctly. - Validated `docs/images/deepwiki-badge.svg` as well-formed XML, byte-identical to the official badge image. - Confirmed line 8 of `README.md` on `dev` is unchanged upstream, so no merge conflict. ## Checklist - [x] Code compiles and all tests pass (docs/asset-only change, no code touched) - [x] `mvn clean install -DskipTests` finished successfully - [x] No new exceptions in the log (N/A) - [x] Docs updated and aligned with English docs (README only, N/A for zh docs) -- 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]
