Fix server readiness for 2.6 tests

[verdie-g]

Since #122, v2.6 tests have been failing with Grpc.Core.RpcException : Status(StatusCode="Unknown", Detail="service unavailable: internal: Milvus Proxy is not ready yet. please wait"). The testcontainer is checking /healthz but it seems like it's not enough. The proposed fix is to send some requests until the server is really ready.

[verdie-g]

Honestly, I'm a bit confused about this test.

[roji]

@verdie-g isn't this something that should be fixed in the milvus testcontainer itself? It's the testcontainer's responsibility to reliably wait until the service (Milvus in this case) is up and ready to handle requests. Do you want to submit a PR against https://github.com/testcontainers/testcontainers-dotnet/tree/develop/src/Testcontainers.Milvus?

[verdie-g]

testcontainers/testcontainers-dotnet#1585

[verdie-g]

@roji the testcontainer PR was merged. I'm copying its content here until it's released.

[roji]

Thanks for doing all this great work @verdie-g! I'll go ahead and merge for now, you can submit another PR once the new testcontainer is available to remove the unneeded stuff.

[roji]

@yhmo @xiaofan-luan any idea what the DCO status check is above? It's "waiting for status to be reported" and blocking merging.

[xiaofan-luan]

https://milvus.io/blog/how-to-contribute-to-milvus-a-quick-start-for-developers.md

git commit -m "Commit of your change" -s

@verdie-g
could you double check you did "-s" to agree with DCO?

[verdie-g]

Thanks @xiaofan-luan, I've added the signoff but I can still see the "DCO Expected — Waiting for status to be reported". Any idea why?