Daniel Shmuglin

any updates?

I did a monkey-patching for myself (attached), but we're using only unary calls (no streaming) plus our use case is very simplistic - tracing. ```js const {AsyncResource} = require('async_hooks'); //...

@murgatroid99 any chance we can make it work at least for the server? I did a monkey-patch on our side, relying on private member `Server#http2ServerList`, however v1.10.x broke my patch...

:up:

My use case with restarts is a test stub — I test some logic (integration test) that is dependent on availability of another gRPC endpoint.

Yes, that's what I ended up using. Just thought to report is as a possible regression. Thanks

we use our custom options for various needs. - message fields annotated with validation options (both for API documentation and runtime validations) - methods and services annotated with some runtime-related...

Also backtracking reference (from `MethodInfo` to `ServiceInfo`) is missing and it is really convenient, especially in `protobuf-ts/runtime-rpc` interceptors. I'm trying to migrate gradually to `protobuf-es` + `@grpc/grpc-js` from `protobut-ts` stack.

@smaye81 I have a workaround for now - I generate a [binary descriptor](https://googleapis.dev/python/protobuf/latest/google/protobuf/descriptor.html) as well and use it at runtime for all the option-bound logic. Thanks

@smaye81 @timostamm > Custom options are available to you during code generation time ([docs](https://github.com/bufbuild/protobuf-es/blob/main/docs/writing_plugins.md#reading-custom-options)). Is there any easy generic way to convert custom options to JSON (as appears in `protobuf-ts`...