DanielLeens commented on PR #12904: URL: https://github.com/apache/seatunnel/pull/12904#issuecomment-6851069727
Thanks @SEZ9 and @Kuzn34. I checked the current `fb542b3e` paths behind the clarification. In `tools/seatunnel-python-sdk/seatunnel/cli.py:1375`, explicit `found:false` terminates polling; a status-less legacy response is tolerated once and repeated absence is reported as a response-shape error (lines 1384-1396). A valid status resets that streak. The `id may be wrong` message at line 1659 belongs to the one-shot diagnose HTTP-404 branch, not this polling loop. `endpoints/jobs.py:90-106` documents the compatibility fallback and rejects non-object responses before inspecting the marker. The UI similarly distinguishes missing-job payloads from transport errors, and its missing-state render retains the job ID. These pointers support the author's F5 clarification; they do not dismiss your independent review. This is a reply to the existing finding ledger on the unchanged head, not a second full review or a claim of new runtime validation. -- 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]
