DanielLeens commented on PR #13012: URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6556406655
Thanks @BryanOnKeys for separating the helper/H2 evidence from the actual MySQL/SeaTunnel integration run. The base-versus-head failure comparison is useful supporting evidence for the Unicode-index defect; it does not replace execution of the new MySQL IT. My source-level clearance on unchanged head `4895cefa0bdef570a243fb4d72e7f800f0e3f443` stands. I also checked the current workflow configuration: the fork now resolves to `MindOfqc/seatunnel`, and its Backend and Build workflows report `active`. The earlier statement that the fork's Actions were disabled is therefore no longer current. There are still zero fork workflow runs for this exact head and no Apache head check rollup in this snapshot, so CI execution, including JDBC part-1, remains unproven. The next step is to trigger the normal current-head Build through the repository's existing PR CI flow and have a write-capable maintainer inspect any approval/dispatch gate. Enabling unrelated scheduled workflows or patching dependencies in this PR is unnecessary. The branch is diverged from dev (ahead 7, behind 20), without a reported content conflict; that metadata alone is not a request for a rebase. No additional production-code change is requested here. -- 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]
