DanielLeens commented on PR #11077:
URL: https://github.com/apache/seatunnel/pull/11077#issuecomment-5658109516
Thanks for the release-note callout and for digging into the `Build` failure
— much appreciated.
One correction on the diagnosis, though: this isn't transient Docker Hub
pull throttling. `minio/minio` was permanently removed from Docker Hub (the
`404 pull access denied ... repository does not exist` you're seeing is the
tell — a rate limit would come back as `429`, not `404`). It hit a bunch of PRs
across the repo around the same time and is already root-caused and fixed on
`dev` via #12287, which switches every `MinIOContainer` usage to the
`quay.io/minio/minio` mirror plus the required
`.asCompatibleSubstituteFor("minio/minio")` call (I checked
`PaimonWithS3IT.java` on current `dev` directly — it already carries that fix,
so `PaimonWithS3IT` should go green once this branch picks it up).
Since this PR's last `dev` sync (`153355ce8c`, 2026-09-08) predates #12287,
re-running the same jobs won't help here — a fresh sync with the latest `dev`
should clear the MinIO-related failures. The other jobs you listed
(`all-connectors-it-2/6/7`, `transform-v2-it-part-1`, `rocketmq-connector-it`)
are separate, already-tracked pre-existing flakes unrelated to this PR's diff
(the `transform-v2-it-part-1`/`AssertSinkWriter` static-counter issue and the
RocketMQ topic-route race have both come up earlier in this same thread), so no
action needed on those beyond the sync.
Nothing here changes my 2026-09-13T10:54:03Z approval of `a9d8464` — this is
a CI-infrastructure note, not a reopened review.
--
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]
