DanielLeens commented on PR #12101: URL: https://github.com/apache/seatunnel/pull/12101#issuecomment-6557473619
Thanks @SEZ9. Here are exact-head hunk pointers, rather than another restatement of the checklist: `SeaTunnelConfValidateCommand.java:189-217` builds the sanitized error/fallback and drops the raw cause only in JSON mode; `:219-221` emits success outside that catch; `ConfigValidationResult.java:73-87` builds Jackson nodes; `DryRunConnectFailureMessageSanitizer.sanitize` checks null before matching. The text-mode classification change is explicitly retained as the compatibility caveat in the full review. For F4/F7, `docs/en/engines/zeta/user-command.md:85-87` says diagnostic stdout can coexist and instructs callers to select the result line, then specifies schemaVersion/valid/phase/errors; the ZH page mirrors that contract. A stronger record-selection example remains optional, not a pure-JSON-stdout promise. The source conclusion is unchanged. The actual CI gate is still [Build workflow-run discovery](https://github.com/apache/seatunnel/runs/121486172557), not a demonstrated source failure. The fork owner should link/start the existing Build for this SHA, enabling workflows only if actually disabled. No verified base fix addresses missing workflow execution, so sync/empty commits or dependency changes are not prescribed. Checked 2026-11-01T11:43:39.197524+00:00; unchanged head `55831abaef1e1aac58988977c1da8e73a27d9417`, base `dev`; compare `diverged`, ahead 6 / behind 74; merge `blocked` / `BLOCKED`; review decision `REVIEW_REQUIRED`. Behind/diverged is recorded independently and does not itself request a sync. Daniel has READ repository permission. -- 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]
