What problem is the feature used to solve?

kratos does not provide client-side request retry logic

References

- [http retry](https://github.com/gojek/heimdall/tree/master/httpclient)
- [gprc retry](https://github.com/grpc-ecosystem/go-grpc-middleware/tree/master/retry)

protobuf.js version: 6.8.8

For enumerations defined in proto3, the switch statement generated by pbjs triggers the eslint warning default-case since there is no default case. This should be added to the list of eslint-disable rules in the header comment of the generated source file.

Introduce

It has been more than three years since SOFARPC was open-sourced on April 10, 2018. RPC-related documents are mainly updated in June 2019. At that time, the document was relatively classic, and the core functions of RPC were introduced relatively clearly. However, with the iterative update of functions and the update of relate

#16398 introduces a validate mode for caches which uses ShardedLmdb::exists (rather than load_bytes_with) for the first time. But because it is always consumed in a batch mode (to check that all files referenced by a cache entry exist), that method should likely be converted into a batch call which [partitions by shard similar to store_bytes_batch](https://github.com/pantsbuild/pants/blo

The title might seem a bit vague but I don't know how to describe it any better tbh :-)

Anyway this is what happened: I got some 500 responses from the schema registry and all I could see in the logs was :

[2020-04-02 16:03:35,048] INFO 100.96.14.58 - - [02/Apr/2020:16:03:34 +0000] "PUT /config/some-topic-value HTTP/1.1" 500 69  502 (io.confluent.rest-utils.requests)

The logs di