MindOfqc commented on PR #13012:
URL: https://github.com/apache/seatunnel/pull/13012#issuecomment-6601795015
Thanks for the careful re-read — glad the source-side work is settled. No
code changes are needed on my side for the review itself.
One correction on the CI side, because the state moved after your review and
it changes what is actually blocking us.
When you reviewed, the head `5ca1cd51` had no check runs at all. That is no
longer the case — as of `2026-11-03T03:06:19Z` the exact head now carries a
`Build` check with conclusion `action_required` and the output title "Workflow
run detection failed":
```
GET
/repos/apache/seatunnel/commits/5ca1cd51294fe9a0d48945f2fb7d1fa728e85b43/check-runs
→ Build completed / action_required (run 125700921983)
→ PR signal completed / success
```
The check body (generated by `.github/workflows/notify_test_workflow.yml`)
spells out the remediation in three ordered steps, and it is worth reading
before we spend effort on a sync:
1. Enable GitHub Actions on the fork if it shows an enable button — the text
explicitly names "a billing or spending-limit hold on the account" as a cause.
2. Start a `Build` run by hand from the fork's Actions tab (or push an empty
commit) — the scheduled `Update build status workflow` then adopts that run for
this check within 15 minutes.
3. Only if the branch is based on an old `dev`, sync the branch to the
latest `dev` and push again.
Step 1 is the one that is actually failing here, and it is outside my
control, so step 3 alone would not move the check. The fork cannot schedule any
workflow at all:
```
POST /repos/MindOfqc/seatunnel/actions/workflows/400087800/dispatches
(Build, workflow_dispatch)
→ 422 {"message":"Actions has been disabled for this repository."}
```
The repository settings API reports the opposite, and re-applying them does
not clear it:
```
GET /repos/MindOfqc/seatunnel/actions/permissions
→ {"enabled":true,"allowed_actions":"all","sha_pinning_required":false}
PUT same → 204 No Content ; GET again → unchanged ; dispatch again → same
422
```
Push events are blocked the same way, so the empty-commit route from step 2
cannot work either. The five commits I pushed to this branch since the block
started produced no run at all — the fork's entire run history stops at
`2026-10-29T18:18:19Z`, and none of their SHAs appears in it:
```
4895cefa (2026-10-31) b70ce8e9 / 431b9d81 (2026-11-02) 59e31563 / 5ca1cd51
(2026-11-02)
→ GET /repos/MindOfqc/seatunnel/actions/runs → total_count=8, newest
2026-10-29T18:18:19Z
(the 8 runs cover aa48ae2fc, 46680e9c7, 69f060b4b, 74e19cec8, 700f909d6,
6d2cdf390, c6ea0b075)
```
This is scoped to this one fork rather than the account — the same dispatch
against another fork of mine fails on the workflow's own trigger list instead,
which means the repository-level Actions service is reachable there:
```
POST /repos/MindOfqc/element-plus/actions/workflows/398436766/dispatches -f
ref=dev
→ 422 {"message":"Workflow does not have 'workflow_dispatch' trigger"}
```
So a branch sync would be needed only after step 1 is unblocked, and doing
it now would not produce a `Build` run. I have therefore deliberately not
rebased or pushed an empty commit — an empty commit is the workaround step 2
offers, and with Actions disabled on the fork it would only add noise to the
branch without starting a run.
I have a GitHub Support case drafted for exactly this block (repo-scoped
Actions disabled while the settings API reports enabled), and I can supply the
raw request/response pairs above plus the fork's run history on request.
For the record, the review content itself is done: `5ca1cd51` is the current
head, `SqlWhereConditionHelperTest` is green locally (127 passed), the MySQL IT
(`jdbc_mysql_where_condition_inserted_column.conf`) is committed but cannot be
executed on this machine — no Docker here, so the IT is CI-only for me — and
the branch is currently 26 commits behind `dev`.
Prepared with an AI coding agent.
--
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]
