DanielLeens commented on PR #12101: URL: https://github.com/apache/seatunnel/pull/12101#issuecomment-6514270799
Thanks @SEZ9. I rechecked the current code behind your checklist. SeaTunnelConfValidateCommand.java:212-217 deliberately drops the raw cause in JSON mode while retaining legacy text diagnostics; :219-221 serializes success outside the validation catch. The shared sanitizer handles null before matching, and structured errors use a non-null fallback. ConfigValidationResult.toJson:73-87 uses Jackson nodes for escaping. Both user-command pages document schemaVersion/valid/phase/errors and explicitly allow diagnostic stdout alongside the result (English :85-87); pure-JSON stdout is not the current advertised contract. My prior full review also explicitly records the exceptional text-mode path-error classification change, rather than claiming byte-for-byte diagnostic compatibility. The remaining result-record selection clarification is Low/nonblocking. I therefore keep my source clearance and respectfully do not reopen those eight source requests from an older checklist. The exact-head Build discovery gate remains actionable: start/link the existing fork Build, enabling workflows only if disabled. No sync-only cure, empty commit or unrelated dependency change is requested. Checked 2026-10-30T03:30:37.151877+00:00; head `55831abaef1e1aac58988977c1da8e73a27d9417`. [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40168278125/job/121480735658)=`SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/121486172557)=`ACTION_REQUIRED`. Base `dev`, `diverged`, ahead 6/behind 61; merge `blocked`. This is an unchanged-head discussion/CI clarification, not another full source review or an effective approval. 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]
