this is happening again and breaking standard system test CI
The standard Discourse plugin system-test CI failed during its shared MinIO environment setup. The MinIO client download returned HTTP 410 before any plugin system tests ran.
just acking this one and I’m looking. seems like the upstream builds have disappeared.
Yeah.
Looks like:
- Both
minio/minioandminio/mcare now archived. - MinIO’s README says “Alternatives:* AIStor Free — Full-featured, standalone edition for community use (free license)”
- MinIO’s README also says “Important: The MinIO community edition is now distributed as source code only. We will no longer provide pre-compiled binary releases for the community version.”
I’m not sure if AIStor is a simple drop-in replacement?
Given this simply just doesn’t work now, is it better to disable this dependency and skip any tests that rely upon it in interim?
I appreciate specs are critical but I believe this is only used on a tiny percentage of tests.
Does this break production in some way? From my analysis, impact looks limited to specs?
I came across something similar when I noticed that Minio is a dependency of one of the services I use, and just yesterday I was evaluating alternatives.
It seems that the lightweight and most developed option is https://garagehq.deuxfleurs.fr/, while the most comprehensive one (still in development and possibly not yet ready for production) is RustFS · GitHub
yeah, RustFS looks like the best potential from a quick look but it’s not drop in either. currently, I’m working on just forking those two repos and creating a workflow that will build the binary for us.
| Capability | Status | Scope |
|---|---|---|
| ACL authorization |  Excluded |
Intentionally unsupported product behavior |