Lin
Lin
I currently need this feature, and it seems like it hasn't been merged yet. Is there anything I can do to help?
Has there been any progress on this issue? I'm facing the same problem.
I also encountered this problem.The provider is dropped after the call to init_tracing is completed, which results in the loss of the weak reference. Extending the lifetime of the provider...
I’m attempting to fix this issue.🙋 https://github.com/nacos-group/nacos-sdk-rust/pull/242
> 但这里的重试主要是初始化链接时候的，应该不是 get_config 的 block。如果 block 住了是否 build() 没正常连上服务端？ 是的，因为可能会有网络原因无法连上服务器
调用是这样的get_config-> get_config_inner_async ->remote_client.send_request ->self.send_request.send_request(grpc_request) ->future::poll_fn(|cx| svc.poll_ready(cx)) 这里poll_ready导致的
> 设置最大连接次数能规避。 但也提个反问，网络问题应该解决它，而应用启动拦截反而是好事？ 可能希望单纯的希望当nacos server端网络连接不通的时候不必强依赖nacos也可以启动起来，因为这样强阻塞线程会让其他流程代码无法往下进行
或许在FailoverConnection send_request里增加一个时间，在指定时间里没有执行成功，返回一次错误