SEPURI-SAI-KRISHNA commented on PR #12290: URL: https://github.com/apache/seatunnel/pull/12290#issuecomment-5658339071
Agreed, and that matches what I found independently before reading this. Syncing now. Two refinements from the attempt 2 logs. `paimon-connector-it` is no longer the Maven resolution failure. That was the signature on attempt 1. On attempt 2 it is `PaimonWithS3IT.startUp:151 ยป ContainerFetch`, the same MinIO pull, so the sync should clear it along with the rest. `Dead links` also came back green on this attempt. On this run every failed leg was MinIO and nothing else: `IcebergSourceIT.startUp:161`, `DatabendIT.startUp:249`, `DatabendCDCSinkIT.startUp:221`, `S3FileWithFilterIT.startUp:76` and `PaimonWithS3IT.startUp:151`. On the registry state, what is observable from outside is that anonymous pulls are denied, rather than that the repository is definitely gone. An anonymous manifest request for `minio/minio` returns 401 UNAUTHORIZED, the same request for `library/alpine` returns 200, and the Hub API reports the `minio/minio` repository as not found. The daemon collapses that into `404 ... repository does not exist or may require 'docker login'`. The distinction only matters in that a Hub credential would be the alternative fix, and the quay mirror is clearly the better one, so nothing here argues against #12287. The comment #12287 adds at the call sites reads the same way, that Docker Hub "no longer serves anonymous/unauthenticated pulls". One thing to expect after the sync: `all-connectors-it-7` will likely still fail, on a different MinIO reference. `S3FileConnectDryRunIT` was added by #12242 at 10:31Z on 09-13, after #12287 was written, and still points at Docker Hub on dev. It sits in `connector-file-s3-e2e`, the same module as `S3FileWithFilterIT`, so that leg stays red until #12302 lands. -- 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]
