Use try-with-resources or close this "HazelcastServerCachingProvider" in a "finally" clause.

Change the implementation or suppress sonar warning

https://sonarcloud.io/project/issues?fileUuids=AW9qkIoKkrN6v4yKaPtE&id=hz-os-master&resolved=false&severities=BLOCKER&types=BUG

As a dask maintainer, I want to trust the code coverage report.

Our coverage badge is a bit misleading showing coverage below 90%. This is due to us not collecting coverage in a few places. Also, we simply have a few modules which are only there for debugging and/or historical reasons

The most relevant parts (scheduler, worker, etc.) do have quite good coverage. I believe the <90% batch does

It seems that the number of joining clients (not the num of computing clients) is fixed in fedml_api/data_preprocessing/**/data_loader and cannot be changed except CIFAR10 datasets.

Here I mean that it seems the total clients is decided by the datasets, rather the input from run_fedavg_distributed_pytorch.sh.

https://github.com/FedML-AI/FedML/blob/3d9fda8d149c95f25ec4898e31df76f035a33b5d/fed

Summary

What change needs making?
Example script on how to use created secret successfully.
I have tried myself using the following code from test
It creates a secret successfully but fails to echo the secrets value.

Use Cases

When would you use this?
when I n

Is your feature request related to a problem? Please describe.
Look at here

If taking just one row with our sorting, we may use GROUP BY and FIRST to solve this problem, it can be a lot faster. Let's add this special handling.

the query!() macro accepts the QueryFilter which is a union of each of the field in the QueryFilter struct.
Right now, you can only specify one variant of the HeaderType enum in the header_type() method for QueryFilter.
This may not be necessary (because we can filter HeaderType in zome_fn level against what is returned from query macro), but may be nice to have if the header_type fiel