SEZ9 commented on PR #10238: URL: https://github.com/apache/seatunnel/pull/10238#issuecomment-5390957034
@DanielLeens Thanks for the clear status — and sorry this one slipped without a direct answer. To answer you plainly: no, the refresh has not happened yet. The head is still `2952d0553`, the conflicts with `dev` are unresolved, and the only `Build` signal attached to this head remains the stale run from July 26 (https://github.com/apache/seatunnel/runs/89797556787), so there is nothing new for you to look at. We're fully aligned on the plan: the code side is settled and the remaining blockers are mechanical — sync with the latest `dev`, resolve the conflicts, push the refreshed head, and let CI produce a result that actually reflects the current StarRocks BE host/port mapping diff. Concrete remaining asks, all on the contributor side: 1. Rebase/merge against the latest `dev` and resolve the reported conflicts. 2. Push the refreshed head so CI runs against the current diff. 3. If any lanes are still red after the refresh, paste the fresh failing job links here so we can narrow them down against the updated base. No action needed from you until then — I'll ping this thread as soon as the refreshed head lands so you can take that final look at the new CI results and we can move toward merge quickly. <!-- streview-comment:498 --> -- 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]
