hutiefang76 commented on PR #12592: URL: https://github.com/apache/seatunnel/pull/12592#issuecomment-6271264919
Updated in `a18e06f02c`. The dev conflict is resolved: both sets of EN/ZH upgrade notes and the incoming MySQL tests are retained. The complete PR diff is still the original 13-file scope, with the DuckDB implementation unchanged by the merge. I reran all 114 DuckDB tests and the existing `JdbcMysqlIT#testDuckDbTimestampPrecisionAutoDdl` against a real MySQL 8.0.43 container. All passed with zero failures/errors/skips, along with root formatting and verify. The description now records the executed MySQL case instead of the earlier local-validation gap; it is generated-DDL/database acceptance, not a full engine pipeline run. Build dispatch for this new head still returns HTTP 422, `Actions has been disabled for this repository`, despite the fork's enabled Actions setting and active Build workflow. Could a maintainer trigger the upstream run? The optional ResultSet retention suggestion remains a separate follow-up. <sub>AI-assisted follow-up for @hutiefang76.</sub> -- 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]
