Klaus Post
Klaus Post
@AdamKorcz I updated the `TB` interface to match Go 1.25 - I did not go deeper into other stuff added to `testing`. There shouldn't be any risk of breakage AFAICT....
We do not provide community support for older MinIO versions. Probably this has already been fixed.
Ah, yeah, missed that. Same thing applies, though. Use latest. Guessing it could be something like #420 or #419 - but hunting bugs in non-current versions is not productive.
That is all I needed to know.
You are doing concurrent operations - a non-deterministic result is to be expected. Listings *may* include objects adding while listing. Listings *may* include items that have been deleted, if deleted...
Provide a proper reproducer. I have no idea what story you are trying to tell here.
How do you know "when ILM is running"?
They are completely independent, so it just feels like correlation, not causation. There is filtering happening on listings that removes objects past expiry. I haven't really dealt with that. @krisis...
It sounds more like your new node is having troubles. Listing quorum isn't really affected by which node is called, except if it has connectivity issues. I don't really see...
Honestly, this seems a crazy amount of code for an extremely specific use-case.