Several small issues that don't deserve their own thread.

Nomad version

Nomad v1.2.6 (a6c6b475db5073e33885377b4a5c733e1161020c)

Operating system and Environment details

N/A

Issue 1

The documentation specifies the Count field of the request body JSON as optional, but it does not explain what behavior should be expected when the field is omitted.

Reproduction st

version:
zh web page：https://www.cloudwego.io/zh/docs/hertz/reference/version/
zh doc：https://github.com/cloudwego/cloudwego.github.io/blob/main/content/zh/docs/hertz/reference/version.md
en folder：https://github.com/cloudwego/cloudwego.github.io/tree/main/content/en/docs/hertz/reference

json:
zh web page：https://www.cloudwego.io/zh/docs/hertz/reference/json/
zh doc：https://github.com/clou

🚀 Feature Request

HF has some logic under the hood that looks at the number of labels in order to decide if whether to use a BCE, CE, or MSE loss.

Splitting up the BERT class based on the loss and making these distinctions as to what loss is used to the user may be more clear. It also aligns with the work of @Landanjs

Note: this may also require creating a separate .loss method in

Is there an existing issue for this?

• I have searched the existing issues

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

Milvus highly rely on etcd for meta operation.
Retry is need since failed to operate on etcd may cause server crash.
To be noticed, the CompareValueAndSwap, CompareVersionAndSwap may no be able to add retry in a no brainer style so we need to

• 目标提升到80%以上

• 如何获取单侧覆盖率：

1. 项目根目录下运行mvn test
2. 项目根目录下用浏览器打开target/site/jacoco/index.html即可查看单侧覆盖率，点进去即可查看详细覆盖情况以作出补充

Hi,

It seems like the HTTP Assert package does not allow me to specify a body to pass in a POST request for example. Looking at the HTTPBody() function, the body argument is set to nil:
req, err := http.NewRequest(method, url+"?"+values.Encode(), nil)

Is this by design, or am I looking at a missing feature?

Cheers,

To make it easier for us to know which charts need to be added still it would be nice to have an overview in the readme

E.g. krajo-mimir-distributed-make-bucket-job-g42xc should be just krajo-mimir-make-bucket-job-g42xc

Install the mimir-distributed chart and see consistency of pod/job names with kubectl get pod