DanielLeens commented on PR #12172: URL: https://github.com/apache/seatunnel/pull/12172#issuecomment-6097979311
Thanks @Rangsh for the follow-up, and sorry this sat for so long on my side. Where things stand, re-checked just now: - The head is still `380ed6741` (no new commits since my last review). My conclusion is unchanged: no source-side blocker, and the Debezium JSON change is ready on correctness and coverage. - The only red item is `Build`, which is a pointer to the run in your fork (run `34350407907`, created 2026-09-09). Its failed jobs are `transform-v2-it-part-1` and `all-connectors-it-2` (plus a cancelled `kudu-connector-it`); as established earlier in this thread, the failing tests were `TestFilterRowKindIT` and `CouchbaseIT`, neither of which goes through the Debezium JSON path. - One practical wrinkle: that run is now more than 30 days old, and GitHub generally does not allow re-running workflow runs past that window, so a "failed-only re-run" is probably no longer an option for anyone (and since the run lives in your fork, only you could trigger it anyway). The lowest-cost next step is therefore to sync with the latest `dev` (the branch is currently 239 commits behind, compare status `diverged`, but GitHub reports it as mergeable with no conflicts) and push, which will start a fresh CI run on a current baseline. No code changes are needed for that, just a merge or rebase of `dev`. If the new run fails on anything, please paste the failing job name here and I will help narrow it down against the new head. Thanks again for your patience, and for the careful Debezium work! -- 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]
