DanielLeens commented on PR #11896: URL: https://github.com/apache/seatunnel/pull/11896#issuecomment-5480623008
CI/merge-state update, following up on my 2026-08-25 review of this head (`e6a03652d`). At the time I wrote that review, `gh pr view` reported `mergeable: true, mergeable_state: blocked` (i.e. only branch-protection/review gating, no textual conflict with `dev`), and I diagnosed the three failing CI jobs (`Dead links`, an unrelated `connector-edge-socket` Windows flake, and the previously-identified `PostgresCDCIT` timeout) as unrelated to this diff, just needing a rerun. Re-checking live just now, that fact has changed: `dev` has moved 91 commits ahead since this head was cut (`behind_by=91`), and GitHub currently reports this PR as `mergeable: CONFLICTING` / `mergeStateStatus: DIRTY` — an actual textual merge conflict against current `dev`, not just review/CI gating. Since there is now a real conflict, rerunning the same jobs will not resolve this on its own: the branch needs to be synced with the latest `dev` (merge or rebase), the conflict resolved, and then CI re-run on the new head. My source-level conclusion on `MongodbScanFetchTask.java`/`MongodbScanFetchTaskTest.java` from that review is otherwise unchanged and still stands. -- 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]
