stag7824 commented on PR #2373:
URL:
https://github.com/apache/datafusion-ballista/pull/2373#issuecomment-5645273550
Thanks for the approval @andygrove.
`test linux crates` went red on the run that followed, but it isn't this
change — all five failures are in `examples/tests/object_store.rs` and they are
image pulls, not assertions:
```
called `Result::unwrap()` on an `Err` value: Client(PullImage {
descriptor: "minio/minio:RELEASE.2025-02-28T09-55-16Z",
err: DockerResponseServerError { status_code: 404,
message: "pull access denied for minio/minio, repository does not exist
..." } })
```
It's the stale-branch version of the problem #2447 just fixed: MinIO
withdrew `minio/minio` from Docker Hub on Sep 11, my run hit that the same
evening, and `ab98c3f` has since pointed the tests at `quay.io/minio/minio`. My
branch was last synced with main on Sep 3, so it was still pulling the
withdrawn image. Re-running wouldn't have helped — the image is genuinely gone
from Docker Hub.
I've merged `upstream/main` (`1d44275`), which brings in that registry
override. No conflicts, and the diff against main is still just the two
`Cargo.toml` files.
Re-checked the forwarding after the merge:
```
$ cargo tree -e features -i ballista-core -p ballista-executor --features
arrow-ipc-optimizations
ballista-core v54.0.0
├── ballista-core feature "arrow-ipc-optimizations"
│ ├── ballista-executor feature "arrow-ipc-optimizations" (command-line)
```
CI on fork PRs needs a maintainer to approve the run, so it will need one
more click when you have a moment.
--
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
