SEZ9 commented on PR #10986: URL: https://github.com/apache/seatunnel/pull/10986#issuecomment-5476201049
Thanks everyone for keeping this thread moving, and thanks @goutamadwant for the status check. To summarize where this PR stands so the author has a clear picture: 1. **Unchanged head**: The current head `1d1397232afc` is still the same revision @DanielLeens already reviewed, so the source-side blockers from that review remain unresolved. 2. **Branch sync**: The branch has diverged from upstream (`ahead_by=5`, `behind_by=309`) and GitHub reports merge conflicts with the latest base. Please sync with the latest `dev` and resolve the conflicts first. 3. **CI gate**: Per DanielLeens' latest recheck, the `Build` gate is now `ACTION_REQUIRED` rather than failing outright, so after the sync we'll need the workflow approved/retriggered to get a clean signal and separate baseline CI noise from real code issues. Concrete asks for the author: - Please confirm whether you're still planning to continue this PR, as @goutamadwant asked. - If yes: rebase on latest `dev`, resolve the merge conflicts, push a follow-up commit addressing the source-side blockers from Daniel's review, and then ping @DanielLeens for a fresh re-review of the new head. - If you're blocked on anything, let us know here — @davidzollo has also offered to help troubleshoot directly, and the community Slack (#contributors channel) is a good place for a quicker back-and-forth. Until those items land, this stays out of merge-ready state. Happy to move quickly on a re-review once there's a new head to look at. <!-- streview-comment:687 --> -- 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]
