foghost
> @ev1lQuark 很赞的需求，另外有一个建议。将 Metrics 模块的被集成能力加强。目前只能启动 dubbo-go 实现的http server 拿到metric。希望可以支持从外部注入 Prometheus Registerer。如果认同，我可以贡献开发。 metric 模块目前已经大致可用了，从某种意义上来说，你这个需求其实可以实现的，目前的 Prometheus registry 实现是需要传入 Registerer 的只不过目前用的默认的全局 Registerer，用户是可以通过扩展覆盖掉原始配置的，但是目前 api 还没完全稳定下来
Protobuf definition: ```protobuf syntax = "proto3"; package org.apache.dubbo.metadata; option go_package = "dubbo.apache.org/dubbo-go/v3/metadata/triple_api"; option java_package = "org.apache.dubbo.metadata"; service MetadataService { rpc GetMetadataInfo(Revision) returns (MetadataInfo) {} } message Revision { string value...
According to https://datatracker.ietf.org/doc/rfc9113/ 5.1.1 Stream identifiers cannot be reused. Long-lived connections can result in an endpoint exhausting the available range of stream identifiers. A client that is unable to establish...
Have you start provider first?
no native-image config found, plz make sure what you have done with native-image
The same thing is happened at https://github.com/apache/dubbo/blob/0553d70899253519bd6fab00fb647eababf1c911/dubbo-rpc/dubbo-rpc-triple/src/main/java/org/apache/dubbo/rpc/stub/StubInvocationUtil.java#L53-L62 maybe we should find a unified way to solve this problem
pls provide more information such as config file or init logic
Hessian2 序列化，你的自定义pojo 有注册到 Hessian2 吗， 像这样： `hessian.RegisterPOJO(&common.URL{})`
demo is 404, it looks like your java server use triple protocol for metadata service, but now we only support dubbo protocol
ref https://github.com/apache/dubbo-go/issues/2403