注册dubbo服务报POLARIS:API_INVALID_ARGUMENT错误码

[Caesaer]

错误日志：
2024-04-23 16:35:57.338 [main ] [reqId:] ERROR c.t.p.d.m.report.PolarisMetadataReport | 55 | [DUBBO] Invalid error code: POLARIS:API_INVALID_ARGUMENT, the format of error code is: X-X (where X is a number)., dubbo version: 3.2.0, current host: 169.254.86.123
2024-04-23 16:35:57.339 [main ] [reqId:] ERROR c.t.p.d.m.report.PolarisMetadataReport | ? | [DUBBO] get service_contract fail, dubbo version: 3.2.0, current host: 169.254.86.123, error code: POLARIS:API_INVALID_ARGUMENT. This may be caused by ERR-1001(API_INVALID_ARGUMENT): service can not be blank, go to to find instructions. RequestBaseEntity{timeoutMs=0} BaseEntity{, service='', namespace='g3'}

不是必现问题，有些项目可以正常注册

[Caesaer]

服务生产者能在北极星的后台看到，但消费者消费不到，想问下是不是和上面的错误有关呢
生产者：

消费报错：
2024-04-24 17:44:31.641 [nio-8180-exec-1] [reqId:] DEBUG com.g3.web.handler.LoggingAspect | 40 | 请求url: 【http://localhost:8180/g3-demo-web/award/insert】,参数:【[AwardVO(id=null, awardCode=testPolaris, awardName=测试polaris调用, awardProject=fdsfdf, awardDate=null, awardMoney=null, memo=null, dateTest=null, attachTest=null, awardSubList=null)]】
2024-04-24 17:44:31.715 [nio-8180-exec-1] [reqId:] WARN o.a.dubbo.rpc.cluster.SingleRouterChain | ? | [DUBBO] No provider available after route for the service g3/com.g3.billcode.api.BillCodeApiService from registry 169.254.12.166 on the consumer 169.254.12.166 using the dubbo version 3.2.0. Router snapshot is below:
[ Parent (Input: 0) (Current Node Output: 0) (Chain Node Output: 0) ] Input: Empty -> Chain Node Output: Empty
[ MockInvokersSelector (Input: 0) (Current Node Output: 0) (Chain Node Output: 0) Router message: Empty invokers. Directly return. ] Current Node Output: Empty, dubbo version: 3.2.0, current host: 169.254.12.166, error code: 2-2. This may be caused by No provider available after route for the service, go to https://dubbo.apache.org/faq/2/2 to find instructions.
2024-04-24 17:44:31.715 [nio-8180-exec-1] [reqId:] WARN o.a.d.r.c.directory.AbstractDirectory | ? | [DUBBO] No provider available after connectivity filter for the service g3/com.g3.billcode.api.BillCodeApiService All validInvokers' size: 0 All routed invokers' size: 0 All invokers' size: 0 from registry 127.0.0.1:8091 on the consumer 169.254.12.166 using the dubbo version 3.2.0., dubbo version: 3.2.0, current host: 169.254.12.166, error code: 2-2. This may be caused by provider server or registry center crashed, go to https://dubbo.apache.org/faq/2/2 to find instructions.

[chuntaojun]

北极星目前没支持 dubbo 消费者上报，另外我看你们用的是 dubbo 的接口级注册发现，元数据中心上报失败应该不影响，第一条报错，可以给一下你的 polaris-server 版本信息吗

[Caesaer]

北极星目前没支持 dubbo 消费者上报，另外我看你们用的是 dubbo 的接口级注册发现，元数据中心上报失败应该不影响，第一条报错，可以给一下你的 polaris-server 版本信息吗

server版本：1.18.0
如果dubbo消费者无法上报的话是不是意味着无法消费dubbo服务？

[chuntaojun]

北极星目前没支持 dubbo 消费者上报，另外我看你们用的是 dubbo 的接口级注册发现，元数据中心上报失败应该不影响，第一条报错，可以给一下你的 polaris-server 版本信息吗

server版本：1.18.0 如果dubbo消费者无法上报的话是不是意味着无法消费dubbo服务？

消费者上报和能不能完成 dubbo 服务调用没有关系，dubbo 服务调用只关心 provider 有没有正常注册