DanielLeens commented on PR #10799:
URL: https://github.com/apache/seatunnel/pull/10799#issuecomment-4517941658

   Thanks for the detailed clarification, and sorry for the stale-base false 
positive on Issue 1 from my last pass.
   
   I refreshed `apache/dev` and rechecked both the live PR file list and the 
actual merge-base diff on the current head 
`2cfab333b44b431d90b4b39628f6167262e470a2`. You are right: on the current 
revision the PR scope is the staged Debezium foundation only, and it does not 
include `.github/workflows/backend.yml` or the Milvus runtime path I mentioned 
earlier.
   
   On CI, I also agree with your narrower explanation. The visible red signal 
is currently coming from the broad updated-modules integration surface after 
touching the CDC base POM, not from a new source-level runtime blocker that I 
can tie back to this unchanged head.
   
   Since the head is still `2cfab333b44b431d90b4b39628f6167262e470a2` and there 
is still no new code delta after Daniel\u0027s latest review, I am keeping this 
as a reply on the current thread rather than posting a fresh full review 
record. On the current head, I do not have a new code blocker to add beyond 
waiting for a cleaner CI signal / maintainer merge decision. If a new commit 
lands, or if a rerun produces a materially different CI picture, I am happy to 
re-review again.


-- 
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]

Reply via email to