protobuf

After PR #1401 merged, many of our sub modules are failing lint, we should fix all of them.

To fix these, take a look at hack/.lintcheck_failures for a list of currently lint failed modules.

You can check a module by removing it from the .lintcheck_failures list and running make fix to auto fix some lint errors.

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.

Now, callback ThreadPoolExecutor is build-in in AsyncRuntime. User can't recognize that the callback executor is full.
We need to add a set method ,so that users can custom their own callback executor.

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