DanielLeens commented on PR #13054: URL: https://github.com/apache/seatunnel/pull/13054#issuecomment-6503359524
The queued signal cited in my source review has completed successfully. There is still no attached aggregate Build result, and fork-run discovery did not establish a completed matching runtime Build. A signal pass alone is not JDBC test acceptance. My source blocker remains cleared; make the existing exact-head fork Build available and have a maintainer reconcile the aggregate/final review gate, without redoing the already addressed transaction-loss fix. Checked 2026-10-29T17:10:59+00:00; head `6394add24f3e23d62524aea81608f47a5889b058`. [Label PRs when reviewed](https://github.com/apache/seatunnel/actions/runs/40912573782/job/123600217831) = `QUEUED`; [Signal pull request update](https://github.com/apache/seatunnel/actions/runs/40890959184/job/123507306998) = `SUCCESS` Comparison: base `dev`, head `6394add24f3e23d62524aea81608f47a5889b058`, `diverged`, ahead 6 / behind 5; GitHub mergeable state `blocked`. Behind/diverged alone is recorded metadata and does not add a sync request. Daniel has READ repository permission. This is a discussion/CI clarification, not a new complete source review, an effective APPROVED event or dismissal of historical requested changes. A write-capable maintainer must perform any required final approval/dismissal. Thanks for keeping the follow-up focused. -- 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]
