Feature-request

配置监听的key发生变更时，按照Source的顺序合并一次，决定最终的value

What problem is the feature used to solve?

有基础配置用于决定所有程序基本行为，以及应用偏好配置决定个别程序特殊行为。
比如所有程序默认日志级别，个别程序做特殊调整。
在偏好配置中日志级别的key删除后，需要使用基础配置的key的配置。

Requirements description of the feature

比如有配置Source: A, B，程序启动的时候会WithSource(A, B)
A里有配置level: debug
程序监听key: level
B新增配置level: warn
到此为止都是正常的，监听拿到了level从debug修改warn
而当B把配置lev

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

Describe the bug

Latest docs suggest using "$regex$DEPRECATED:\\s*" for filtering deprecation log messages.

Having this configuration in the pants.toml file:

[GLOBAL]
ignore_warnings = ["$regex$DEPRECATED:\\s*"]

Results in warning messages printed:

10:28:38.

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