rwzdk commented on PR #13020:
URL: https://github.com/apache/seatunnel/pull/13020#issuecomment-6515613295
Status note on `bb27e280` so the record stays accurate: GitHub Actions has
been switched off on my fork since last night, so this head has no fork `Build`
at all — `POST /repos/rwzdk/seatunnel/actions/workflows/400087800/dispatches`
returns `422 {"message":"Actions has been disabled for this repository."}` even
though `GET /repos/rwzdk/seatunnel/actions/permissions` still answers
`{"enabled":true,"allowed_actions":"all"}`, and the workflow registration on my
other forks (e.g. `rwzdk/trpc`, previously 20 workflows) now lists 0. `GET
/user` on this account reports `email: null, verified_email: null`, which is
the condition under which GitHub suspends Actions, so it needs the account
email re-verified — an account-side fix, not something I can do from the repo.
Practical consequence: the new `/jsonpath/ragged` case in `HttpIT` cannot be
shown green here until Actions returns. The local evidence stays what I quoted
(`connector-http-base` `Tests run: 74, Failures: 0, Errors: 0` on JDK 17, which
covers the padded rows and the factory routing); the e2e job itself needs
Docker, which this machine has none of. I am not adding further commits or
empty pushes to force a check to appear — once Actions is back I will
re-dispatch the `Build` for the current head and report the result.
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]
