DanielLeens commented on PR #12251: URL: https://github.com/apache/seatunnel/pull/12251#issuecomment-6557117609
Thanks for keeping this contribution moving. I need to update the merge-gate information on unchanged head `eb95e7ec00dbcbcd5bb927fed7cf3f2fcd9e6d63`: GitHub currently reports actual content conflicts with `dev` (`CONFLICTING` / `DIRTY`). This supersedes the earlier no-conflict/blocked snapshot; it is a content-conflict request, not a sync request based solely on branch age. Please sync the latest `dev` and resolve the conflicts while preserving both this PR's intended change and the intervening upstream changes, then obtain required checks on the resulting head. My latest source-level clearance remains unchanged. The existing runner-loss CI failure is separate from this content conflict; do not patch JsonPath code to chase that infrastructure signal. The [preceding complete source review](https://github.com/apache/seatunnel/pull/12251#pullrequestreview-5720918311) remains the source assessment; this is a gate clarification, not another full review or a new list of source findings. Current existing-head checks: [Build](https://github.com/apache/seatunnel/runs/123937465428)=FAILURE. Compare `diverged`, ahead 19 / behind 9. Checked 2026-11-01T11:08:13.478002+00:00. Daniel has READ repository permission; final effective approval/dismissal and merge belong to a write-capable maintainer. Happy to review the resulting head once the conflict is resolved. -- 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]
