DanielLeens commented on issue #12627: URL: https://github.com/apache/seatunnel/issues/12627#issuecomment-5994183726
Classification: F / seatunnel-cli failure-diagnosis fidelity. Thanks for isolating the difference between the local tail capture and the repair path. I checked #12628 against the report. Parsing the complete failure before shortening it, then retaining the tail of an oversized Java trace, is the right boundary: the parsed error code/description survives and the raw excerpt still contains the innermost `Caused by`. The patch also redacts both the parsed fields and the excerpt before they enter the repair prompt. The regression tests cover the important failure mode (a code and root cause beyond the 3,000-character boundary), the tail rather than head selection, and the exact-limit/short-trace controls. The PR's Build and Python checks are currently successful, but it remains under review and is not in `dev` yet. Please keep this issue open until #12628 merges; there is no need for a second implementation path. -- 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]
