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

   Thanks for the follow-up. I rechecked the current active head on August 3, 
2026.
   
   From Daniel's side, the latest source review on this head was already down 
to CI / merge gates only. On the current active diff, I still only see the two 
Kafka source files for the bounded split-completion fix:
   - 
`seatunnel-connectors-v2/connector-kafka/src/main/java/org/apache/seatunnel/connectors/seatunnel/kafka/source/KafkaPartitionSplitReader.java`
   - 
`seatunnel-connectors-v2/connector-kafka/src/test/java/org/apache/seatunnel/connectors/seatunnel/kafka/source/KafkaPartitionSplitReaderTest.java`
   
   The branch is now `diverged` and behind `dev` (`behind_by=85`). The only 
visible `Build` result attached to this head is still the old run from July 19, 
2026: https://github.com/apache/seatunnel/runs/88207895989 . In the contributor 
workflow behind that check, the visible non-green jobs include `Run / Dead 
links`, `Run / unit-test (11, ubuntu-latest)`, and `Run / 
updated-modules-integration-test-part-1 (8, ubuntu-latest)`. Those gates do not 
line up directly with the current two-file Kafka split-reader diff.
   
   So the lowest-cost next step here is to sync with the latest `dev` and rerun 
CI on the refreshed branch first. If the same lanes are still red after that 
refresh, please paste the fresh failing job links here and I can help narrow 
them down further.


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