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

   Thanks @SEZ9. I queried all fork workflow runs for the exact head 
de507b8e2c7814f2d2f5bba6256c1946e9562db9: the only matching Build returned is 
DanielLeens/seatunnel run 38351240468, completed with failure on October 14, 
attempt 1. I could not find a newer matching queued/requeued run, so that claim 
is not yet confirmed. In the retrieved failed logs, Dead links gets HTTP 429 
from the DeepWiki page/badge; the JDK 8 transform and Pub/Sub jobs fail on 
Maven Central connection resets/cached failed BOM downloads, not a demonstrated 
slot-usage assertion. Other failed engine jobs still need their own reports, so 
I am not calling the whole run unrelated or passed. Please rerun the affected 
existing jobs after the transfer/rate-limit conditions clear, or link the 
intended newer exact-head run. Latest dev uses a local badge but still links 
the remote project page; a sync alone does not repair external 429 or 
connection resets. Keep dependencies unchanged for those transfer failures. 
Separat
 ely, Finding 1 from my source review (forwarded operation waits on the 
aggregation future) remains a merge blocker; a green retry would not clear it.
   
   Checked 2026-10-29T17:14:27+00:00; head 
`de507b8e2c7814f2d2f5bba6256c1946e9562db9`. [Notify test 
workflow](https://github.com/apache/seatunnel/actions/runs/38351242553/job/115143907640)
 = `SUCCESS`; 
[labeler](https://github.com/apache/seatunnel/actions/runs/38351242528/job/115143907282)
 = `SUCCESS`; [Build](https://github.com/apache/seatunnel/runs/115143931893) = 
`FAILURE`
   
   Comparison: base `dev`, head `de507b8e2c7814f2d2f5bba6256c1946e9562db9`, 
`diverged`, ahead 11 / behind 291; GitHub mergeable state `blocked`. 
Behind/diverged alone is recorded metadata and does not add a sync request.
   
   Daniel has READ repository permission. This is a discussion/CI 
clarification, not a new complete source review, an effective APPROVED event or 
dismissal of historical requested changes. A write-capable maintainer must 
perform any required final approval/dismissal. Thanks for keeping the follow-up 
focused.
   


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