DanielLeens commented on PR #12877: URL: https://github.com/apache/seatunnel/pull/12877#issuecomment-6282876074
Thanks for the quick follow-up and for trying the dispatch, @hutiefang76. Good to hear the two-database PostgreSQL regression and the catalog routing tests pass locally. On the CI side: the `HTTP 422: Actions has been disabled for this repository` response means GitHub Actions is switched off at the fork level, so neither the dispatch nor a push can create the `Build` run there. Maintainers cannot start that run on your behalf, because the apache-side `Build` check only looks up and mirrors the run that lives in your fork. These steps usually fix it: 1. Open the fork's **Settings > Actions > General** and select "Allow all actions and reusable workflows" (the fork-level policy must not be "Disable actions"). 2. Open the fork's **Actions** tab; if GitHub shows the banner "Workflows aren't being run on this forked repository", click "I understand my workflows, go ahead and enable them". 3. Make sure the `Build` workflow is enabled in the left sidebar, then push an empty commit to the PR branch (or use "Run workflow" on the branch). The apache-side `Build` check should then pick the run up. One heads-up so you are not surprised by the first result: this PR touches `connector-jdbc`, and `dev` currently has a known unrelated unit-test failure in `JdbcOptionRuleCompletenessTest.testSinkRuleDeclaresAllSinkOptions` (unknown option key `numeric_special_value_as_null`, tracked in #12874 with the fix in #12875, still open). Until #12875 is merged and you sync the latest `dev`, the `unit-test` legs may fail on that test regardless of this change; if that is the only failure, it is not caused by your diff. My earlier review still stands: no code-level blockers, and the only remaining item is a green `Build` on the current head. -- 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]
