DanielLeens commented on PR #11556: URL: https://github.com/apache/seatunnel/pull/11556#issuecomment-6359794293
Thanks for the clear status update, @davidzollo. I re-checked live just now: the head is still `dbc53649a3c1` (the same head I reviewed in my last full review), and the upstream `Build` check on this exact head now reports SUCCESS, together with `labeler` and `Notify test workflow`. That was the only gate I had left open (my last review noted the fork Build was still in progress), so there is nothing further from me on the source side: my conclusion stays Ready to merge. The two Medium follow-ups from that review (per-split backfill slot create/drop cost, and the deterministic backfill slot name after a reader crash) remain non-blocking and fine to track separately. One process note: the earlier CHANGES_REQUESTED review from me is still visible on the PR. All of my technical blockers from that review are cleared, but I do not have write-level review controls, so a maintainer with write access will need to do the final approve or dismiss before merge-queue entry. The branch is mergeable with no conflicts (12 commits behind `dev` is metadata only, no sync needed). Thanks again for the persistent work on this correctness fix. -- 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]
