Giuseppe

Any news on this? It's the only dependency we have which links `testing`

> If you observed an issue and used DNS entries in the cluster file you might have hit: [apple/foundationdb#11222](https://github.com/apple/foundationdb/issues/11222). Especially in the case when the coordinators are not reachable. Commenting...

Sure! that function `fdb_stop_network` is indeed not actively called from the Go binding, but perhaps a destructor on the C binding calls it? I cannot explain this, but since the...

Also related: https://github.com/FoundationDB/fdb-kubernetes-operator/issues/1950 NOTE: the simplification I did [here](https://github.com/apple/foundationdb/pull/11221) does not solve the issue, but finding a way to serialize `fdb_run_network()`/`fdb_stop_network()` will solve it.

Easiest way you can reproduce it is probably by making a few separate Go packages, and start 20-30 FDB client connections from the tests in each of them.

It looks like `{...}` is an expression used for formatting, will remove it. Edit: done.

> Could you please verify if there are any other processes/tools running in our setup? I was not able to reproduce the issue. Is it possible that you ran `fdbcli`...

I see, thanks for the explanation; isn't operator also using `fdbcli` as a fallback way to read status? I can check in logs if it's actually doing that, for some...

Thanks for the fix! I noticed just now that it was merged; I could not reproduce the issue and generally I only run `fdbcli` on the pods to check status,...

Thanks @cwaldren-ld! I confirm that with v7 it's no more there :tada: binaries will be smaller now.