[servicecomb-java-chassis] branch master updated: [SCB-1710] catch the throwable from the scheduled pulling task (#1516)

This is an automated email from the ASF dual-hosted git repository. liubao pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git The following commit(s) were added to refs/heads/master by this push: new 99b6833 [SCB-1710] catch the

[GitHub] [servicecomb-java-chassis] liubao68 merged pull request #1516: [SCB-1710] catch the throwable from the scheduled pulling task

liubao68 merged pull request #1516: [SCB-1710] catch the throwable from the scheduled pulling task URL: https://github.com/apache/servicecomb-java-chassis/pull/1516 This is an automated message from the Apache Git Service.

[GitHub] [servicecomb-java-chassis] zhufeizzz opened a new issue #1525: CSE能支持服务端异步吗？

zhufeizzz opened a new issue #1525: CSE能支持服务端异步吗？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1525 类似于SpringMVC的@Async注解，长时间运行的服务，不需要返回值。 AsyncRestTemplate支持客户端异步，实际还是占用Http请求，客户端服务端保持连接。 没找到相关的说明，难道一定要在服务端代码里面自己放到异步队列？

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #1523: 故障注入功能配置生效问题

liubao68 commented on issue #1523: 故障注入功能配置生效问题 URL: https://github.com/apache/servicecomb-java-chassis/issues/1523#issuecomment-573287038 java-chassis的故障注入都是通过[Hanlders](https://github.com/apache/servicecomb-java-chassis/tree/master/handlers/handler-fault-injection)实现的，

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #1522: 接口返回值定义的是ResponseEntity，为什么返回值的Body为空？

liubao68 commented on issue #1522: 接口返回值定义的是ResponseEntity，为什么返回值的Body为空？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1522#issuecomment-573287185 能将完整的接口原型定义和客户端调用方式的代码贴一下吗？ This is an automated message

[GitHub] [servicecomb-java-chassis] liubao68 merged pull request #1510: [SCB-1705] Update javax.servlet to jakarta.servlet

liubao68 merged pull request #1510: [SCB-1705] Update javax.servlet to jakarta.servlet URL: https://github.com/apache/servicecomb-java-chassis/pull/1510 This is an automated message from the Apache Git Service. To respond

[servicecomb-java-chassis] branch master updated: [SCB-1705] Update javax.servlet to jakarta.servlet (#1510)

This is an automated email from the ASF dual-hosted git repository. liubao pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-java-chassis.git The following commit(s) were added to refs/heads/master by this push: new af7d398 [SCB-1705] Update

[GitHub] [servicecomb-java-chassis] JangNum closed issue #1513: 探针埋点问题

JangNum closed issue #1513: 探针埋点问题 URL: https://github.com/apache/servicecomb-java-chassis/issues/1513 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

[GitHub] [servicecomb-java-chassis] JangNum commented on issue #1513: 探针埋点问题

JangNum commented on issue #1513: 探针埋点问题 URL: https://github.com/apache/servicecomb-java-chassis/issues/1513#issuecomment-573275299 > 你可以看下一个RPC调用的[运行图](http://servicecomb.apache.org/cn/docs/open-design/) 。 > > 客户端选择endpoint是在LoadBalanceHandler里面做的，然后地址信息会存到Context里面，其他Handler也会获取到。

[GitHub] [servicecomb-java-chassis] zhufeizzz commented on issue #1525: CSE能支持服务端异步吗？

zhufeizzz commented on issue #1525: CSE能支持服务端异步吗？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1525#issuecomment-573291100 > 不用。 java-chassis的运行机制和SpringMVC不同。 默认情况下，java-chassis的业务执行都是在独立线程池执行，不占用http请求。 不需要`@async`标签。

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #1519: Unhandled exception to service ConfigQueryService schema application

liubao68 commented on issue #1519: Unhandled exception to service ConfigQueryService schema application URL: https://github.com/apache/servicecomb-java-chassis/issues/1519#issuecomment-573260863 Sorry, github will not load images sometimes, I cannot see your logs. Maybe you need to check

[GitHub] [servicecomb-java-chassis] JangNum opened a new issue #1523: 故障注入功能配置生效问题

JangNum opened a new issue #1523: 故障注入功能配置生效问题 URL: https://github.com/apache/servicecomb-java-chassis/issues/1523 请问，通过修改配置对微服务进行故障注入时，故障注入配置生效的耗时是多少？ 需要重启应用吗？ This is an automated message from the Apache Git Service. To

[GitHub] [servicecomb-java-chassis] JangNum commented on issue #1523: 故障注入功能配置生效问题

JangNum commented on issue #1523: 故障注入功能配置生效问题 URL: https://github.com/apache/servicecomb-java-chassis/issues/1523#issuecomment-573290864 > java-chassis的故障注入都是通过[Hanlders](https://github.com/apache/servicecomb-java-chassis/tree/master/handlers/handler-fault-injection)实现的，

[GitHub] [servicecomb-java-chassis] AngLi2 opened a new pull request #1521: [SCB-1715] Fix idleTimeout not work in client side without keepaliveT…

AngLi2 opened a new pull request #1521: [SCB-1715] Fix idleTimeout not work in client side without keepaliveT… URL: https://github.com/apache/servicecomb-java-chassis/pull/1521 …imeout set Follow this checklist to help us incorporate your contribution quickly and easily: -

[GitHub] [servicecomb-java-chassis] liubao68 commented on issue #1525: CSE能支持服务端异步吗？

liubao68 commented on issue #1525: CSE能支持服务端异步吗？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1525#issuecomment-573287538 不用。 java-chassis的运行机制和SpringMVC不同。 默认情况下，java-chassis的业务执行都是在独立线程池执行，不占用http请求。 不需要```@async```标签。

[GitHub] [servicecomb-service-center] coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically

coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892762 [](https://coveralls.io/builds/28041798)

[GitHub] [servicecomb-service-center] coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically

coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892762 [](https://coveralls.io/builds/28041814)

[GitHub] [servicecomb-service-center] tianxiaoliang merged pull request #619: SCB-1712 Reset kv cache periodically

tianxiaoliang merged pull request #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619 This is an automated message from the Apache Git Service. To respond to the

[GitHub] [servicecomb-java-chassis] yhs0092 commented on issue #1525: CSE能支持服务端异步吗？

yhs0092 commented on issue #1525: CSE能支持服务端异步吗？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1525#issuecomment-573287355 Java-Chassis的异步资料在[这里](https://docs.servicecomb.io/java-chassis/zh_CN/general-development/reactive.html)，Java-Chassis叫这种模式 "Reactive"

[GitHub] [servicecomb-service-center] codecov-io edited a comment on issue #619: SCB-1712 Reset kv cache periodically

codecov-io edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892791 # [Codecov](https://codecov.io/gh/apache/servicecomb-service-center/pull/619?src=pr=h1) Report > Merging

[GitHub] [servicecomb-service-center] codecov-io edited a comment on issue #619: SCB-1712 Reset kv cache periodically

codecov-io edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892791 # [Codecov](https://codecov.io/gh/apache/servicecomb-service-center/pull/619?src=pr=h1) Report > Merging

[servicecomb-service-center] branch master updated: SCB-1712 Reset kv cache periodically (#619)

This is an automated email from the ASF dual-hosted git repository. tianxiaoliang pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/servicecomb-service-center.git The following commit(s) were added to refs/heads/master by this push: new d9eceb7 SCB-1712

[GitHub] [servicecomb-java-chassis] whuxiari opened a new issue #1522: 接口返回值定义的是ResponseEntity，为什么返回值的Body为空？

whuxiari opened a new issue #1522: 接口返回值定义的是ResponseEntity，为什么返回值的Body为空？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1522 返回代码参考：return ResponseEntity.status(status).body(message)； This is an automated

[GitHub] [servicecomb-java-chassis] AngLi2 opened a new pull request #1524: [SCB-1716] Fix high cpu load when there are too many instances

AngLi2 opened a new pull request #1524: [SCB-1716] Fix high cpu load when there are too many instances URL: https://github.com/apache/servicecomb-java-chassis/pull/1524 Follow this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a

[GitHub] [servicecomb-java-chassis] zhufeizzz edited a comment on issue #1525: CSE能支持服务端异步吗？

zhufeizzz edited a comment on issue #1525: CSE能支持服务端异步吗？ URL: https://github.com/apache/servicecomb-java-chassis/issues/1525#issuecomment-573291100 > 不用。 java-chassis的运行机制和SpringMVC不同。 默认情况下，java-chassis的业务执行都是在独立线程池执行，不占用http请求。 不需要`@async`标签。

[GitHub] [servicecomb-java-chassis] coveralls commented on issue #1518: [SCB-1711] support kie

coveralls commented on issue #1518: [SCB-1711] support kie URL: https://github.com/apache/servicecomb-java-chassis/pull/1518#issuecomment-572986333 [](https://coveralls.io/builds/28025942) Coverage decreased (-0.8%)

[GitHub] [servicecomb-service-center] sxcooler commented on issue #614: 可否增加一个开发模式?

sxcooler commented on issue #614: 可否增加一个开发模式? URL: https://github.com/apache/servicecomb-service-center/issues/614#issuecomment-573002027 @little-cui 感谢您提供的思路，我之前的想法也欠考虑，打扰了。 This is an automated message from the Apache Git

[GitHub] [servicecomb-service-center] little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572917960 确认下你调用的是watcher接口还是listwatcher？

[GitHub] [servicecomb-service-center] little-cui commented on issue #614: 可否增加一个开发模式?

little-cui commented on issue #614: 可否增加一个开发模式? URL: https://github.com/apache/servicecomb-service-center/issues/614#issuecomment-572918706 这个问题很有意思，我想应该需要配套你使用的SDK实现，因为service center本身不会做负载均衡，也不存在流量导入问题。另外，我建议你可以通过把开发状态注册到实例信息中，消费时，通过实例的这个状态属性进行判断是否路由

[GitHub] [servicecomb-service-center] little-cui commented on issue #601: go: github.com/kubernetes/client-go@v2.0.0-alpha.0.0.20180817174322-745ca8300397+incompatible: invalid pseudo-version: precedi

little-cui commented on issue #601: go: github.com/kubernetes/client-go@v2.0.0-alpha.0.0.20180817174322-745ca8300397+incompatible: invalid pseudo-version: preceding tag (v2.0.0-alpha.0) not found URL: https://github.com/apache/servicecomb-service-center/issues/601#issuecomment-572919851

[GitHub] [servicecomb-service-center] little-cui commented on issue #584: 依赖关系异步维护机制存在的问题

little-cui commented on issue #584: 依赖关系异步维护机制存在的问题 URL: https://github.com/apache/servicecomb-service-center/issues/584#issuecomment-572921202 A在于B建立依赖的这段时间内，的确会接受不到信息，你可以描述下你的使用场景吗？因为基于servicecomb的SDK，会周期性访问服务中心，以拿到最新实例，属于一种补偿机制

[GitHub] [servicecomb-service-center] Shonminh commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

Shonminh commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572921089 1. 这个issue写的是watcher的接口的，但是其实我也试了listwatcher接口. 2. 我填的是提供方的

[GitHub] [servicecomb-service-center] little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572921665 这两个接口的区别仅仅在于首次watch服务中心时listwatch会返回服务消费方关心的全量实例信息。

[GitHub] [servicecomb-service-center] Shonminh commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

Shonminh commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572922810 那么在使用watcher接口的时候，如何指定我需要关心的服务提供者？是需要配置dependency吗？

[GitHub] [servicecomb-service-center] little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572925518 这是两个流程：

[GitHub] [servicecomb-service-center] goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572928016 > 这是两个流程： >

[GitHub] [servicecomb-service-center] goldbeef commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

goldbeef commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572928016 > 这是两个流程： >

[GitHub] [servicecomb-service-center] goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572928016 > 这是两个流程： >

[GitHub] [servicecomb-service-center] goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

goldbeef edited a comment on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572928016 > 这是两个流程： >

[GitHub] [servicecomb-service-center] little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包

little-cui commented on issue #620: 使用/v4/{project}/registry/microservices/{serviceId}/watcher无法收到回包 URL: https://github.com/apache/servicecomb-service-center/issues/620#issuecomment-572929947 err = registryClient.WatchMicroService(sid,

[GitHub] [servicecomb-service-center] coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically

coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892762 [](https://coveralls.io/builds/28023356)

[GitHub] [servicecomb-service-center] coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically

coveralls edited a comment on issue #619: SCB-1712 Reset kv cache periodically URL: https://github.com/apache/servicecomb-service-center/pull/619#issuecomment-572892762 [](https://coveralls.io/builds/28023441)