DanielLeens commented on PR #12862: URL: https://github.com/apache/seatunnel/pull/12862#issuecomment-6557310812
Thanks again. I need to correct the upstream status in my previous CI follow-up: [#13030](https://github.com/apache/seatunnel/pull/13030) is now merged as [d2fc2079035](https://github.com/apache/seatunnel/commit/d2fc207903516c23f98f52f073e28c1cd63fe2f0), while [#13028](https://github.com/apache/seatunnel/pull/13028) closed without merging. My earlier statement that both were still open is obsolete. The blocking execution remains unit-test (17, ubuntu-latest), [job 123297627304](https://github.com/SEPURI-SAI-KRISHNA/seatunnel/actions/runs/40828465494/job/123297627304), with the previously inspected PhysicalVertexTest startup/port-binding failure; the cancelled connector shard is a separate unfinished gate. I read the merged #13030 patch: it changes HTTP-port allocation in OptionRulesApiTest and RestApiSubmitJobStartWithSavePointTest, not the failing PhysicalVertexTest fixture. That is a related shared-test improvement, not proof that this particular failed startup is cured by syncing. Please avoid unrelated Spark/engine patches in this decimal PR. After checking that no newer Build is active, rerun the failed job(s); if startup still fails, retain its new port/startup diagnostics for an exact attribution. My Spark decimal source clearance remains unchanged. This is an upstream/CI fact correction, not a new list of source findings or an effective maintainer approval. Checked 2026-11-01T11:27:02.063637+00:00; unchanged head `1ce4e26cdbdcac4cf2d901c807463fe82cdf2822`. Current checks: [Build](https://github.com/apache/seatunnel/runs/123363531370)=FAILURE. Base `dev`, compare `diverged`, ahead 3 / behind 21; merge `UNKNOWN` / `REVIEW_REQUIRED`. Drift is recorded independently; it does not itself request synchronization. Daniel has READ permission. This is a CI/merge-gate clarification, not another full source review, effective approval or dismissal. -- 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]
