[GitHub] [servicecomb-mesher] dependabot[bot] opened a new pull request, #156: Bump github.com/prometheus/client_golang from 0.9.1 to 1.11.1

2023-02-14 Thread via GitHub


dependabot[bot] opened a new pull request, #156:
URL: https://github.com/apache/servicecomb-mesher/pull/156

   Bumps 
[github.com/prometheus/client_golang](https://github.com/prometheus/client_golang)
 from 0.9.1 to 1.11.1.
   
   Release notes
   Sourced from https://github.com/prometheus/client_golang/releases";>github.com/prometheus/client_golang's
 releases.
   
   1.11.1 / 2022-02-15
   
   [SECURITY FIX] promhttp: Check validity of method and code label values 
https://github-redirect.dependabot.com/prometheus/client_golang/pull/987";>prometheus/client_golang#987
 (Addressed https://github.com/prometheus/client_golang/security/advisories/GHSA-cg3q-j54f-5p7p";>CVE-2022-21698)
   
   What's Changed
   
   promhttp: Check validity of method and code label values by https://github.com/bwplotka";>@​bwplotka and https://github.com/kakkoyun";>@​kakkoyun in  https://github-redirect.dependabot.com/prometheus/client_golang/pull/987";>prometheus/client_golang#987
   
   Full Changelog: https://github.com/prometheus/client_golang/compare/v1.11.0...v1.11.1";>https://github.com/prometheus/client_golang/compare/v1.11.0...v1.11.1
   v1.11.0 / 2021-06-07
   
   [CHANGE] Add new collectors package. https://github-redirect.dependabot.com/prometheus/client_golang/issues/862";>#862
   [CHANGE] prometheus.NewExpvarCollector is deprecated, use 
collectors.NewExpvarCollector instead. https://github-redirect.dependabot.com/prometheus/client_golang/issues/862";>#862
   [CHANGE] prometheus.NewGoCollector is deprecated, use 
collectors.NewGoCollector instead. https://github-redirect.dependabot.com/prometheus/client_golang/issues/862";>#862
   [CHANGE] prometheus.NewBuildInfoCollector is deprecated, 
use collectors.NewBuildInfoCollector instead. https://github-redirect.dependabot.com/prometheus/client_golang/issues/862";>#862
   [FEATURE] Add new collector for database/sql#DBStats. https://github-redirect.dependabot.com/prometheus/client_golang/issues/866";>#866
   [FEATURE] API client: Add exemplars API support. https://github-redirect.dependabot.com/prometheus/client_golang/issues/861";>#861
   [ENHANCEMENT] API client: Add newer fields to Rules API. https://github-redirect.dependabot.com/prometheus/client_golang/issues/855";>#855
   [ENHANCEMENT] API client: Add missing fields to Targets API. https://github-redirect.dependabot.com/prometheus/client_golang/issues/856";>#856
   
   What's Changed
   
   Synchronize common files from prometheus/prometheus by https://github.com/prombot";>@​prombot in https://github-redirect.dependabot.com/prometheus/client_golang/pull/846";>prometheus/client_golang#846
   Synchronize common files from prometheus/prometheus by https://github.com/prombot";>@​prombot in https://github-redirect.dependabot.com/prometheus/client_golang/pull/849";>prometheus/client_golang#849
   Synchronize common files from prometheus/prometheus by https://github.com/prombot";>@​prombot in https://github-redirect.dependabot.com/prometheus/client_golang/pull/853";>prometheus/client_golang#853
   Add newer fields to Rules API by https://github.com/gouthamve";>@​gouthamve in https://github-redirect.dependabot.com/prometheus/client_golang/pull/855";>prometheus/client_golang#855
   Add missing fields to targets API by https://github.com/yeya24";>@​yeya24 in https://github-redirect.dependabot.com/prometheus/client_golang/pull/856";>prometheus/client_golang#856
   Synchronize common files from prometheus/prometheus by https://github.com/prombot";>@​prombot in https://github-redirect.dependabot.com/prometheus/client_golang/pull/857";>prometheus/client_golang#857
   Add exemplars API support by https://github.com/yeya24";>@​yeya24 in https://github-redirect.dependabot.com/prometheus/client_golang/pull/861";>prometheus/client_golang#861
   Improve description of MaxAge in summary docs by https://github.com/Dean-Coakley";>@​Dean-Coakley in https://github-redirect.dependabot.com/prometheus/client_golang/pull/864";>prometheus/client_golang#864
   Add new collectors package by https://github.com/johejo";>@​johejo in https://github-redirect.dependabot.com/prometheus/client_golang/pull/862";>prometheus/client_golang#862
   Add collector for database/sql#DBStats by https://github.com/johejo";>@​johejo in https://github-redirect.dependabot.com/prometheus/client_golang/pull/866";>prometheus/client_golang#866
   Make dbStatsCollector more DRY by https://github.com/beorn7";>@​beorn7 in https://github-redirect.dependabot.com/prometheus/client_golang/pull/867";>prometheus/client_golang#867
   Change maintainers from https://github.com/beorn7";>@​beorn7 to @bwplotka/https://github.com/kakkoyun";>@​kakkoyun by https://github.com/beorn7";>@​beorn7 in https://github-redirect.dependabot.com/prometheus/client_golang/pull/873";>prometheus/client_golang#873
   Document implications of negative observations by https://github.com/beorn7";>@​beorn7 in https://github-redirect.dependabot.com/prometheus/client_golang/pull/871";>prometheus/client_golang

[GitHub] [servicecomb-mesher] dependabot[bot] opened a new pull request, #157: Bump golang.org/x/net from 0.0.0-20201209123823-ac852fbbde11 to 0.7.0

2023-02-24 Thread via GitHub


dependabot[bot] opened a new pull request, #157:
URL: https://github.com/apache/servicecomb-mesher/pull/157

   Bumps [golang.org/x/net](https://github.com/golang/net) from 
0.0.0-20201209123823-ac852fbbde11 to 0.7.0.
   
   Commits
   
   See full diff in https://github.com/golang/net/commits/v0.7.0";>compare view
   
   
   
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=golang.org/x/net&package-manager=go_modules&previous-version=0.0.0-20201209123823-ac852fbbde11&new-version=0.7.0)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   
   Dependabot commands and options
   
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot merge` will merge this PR after your CI passes on it
   - `@dependabot squash and merge` will squash and merge this PR after your CI 
passes on it
   - `@dependabot cancel merge` will cancel a previously requested merge and 
block automerging
   - `@dependabot reopen` will reopen this PR if it is closed
   - `@dependabot close` will close this PR and stop Dependabot recreating it. 
You can achieve the same result by closing it manually
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   - `@dependabot use these labels` will set the current labels as the default 
for future PRs for this repo and language
   - `@dependabot use these reviewers` will set the current reviewers as the 
default for future PRs for this repo and language
   - `@dependabot use these assignees` will set the current assignees as the 
default for future PRs for this repo and language
   - `@dependabot use this milestone` will set the current milestone as the 
default for future PRs for this repo and language
   
   You can disable automated security fix PRs for this repo from the [Security 
Alerts page](https://github.com/apache/servicecomb-mesher/network/alerts).
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] shri-arunraj opened a new issue, #158: How to register schema in mesher to make intercalls from other microservices.

2023-03-01 Thread via GitHub


shri-arunraj opened a new issue, #158:
URL: https://github.com/apache/servicecomb-mesher/issues/158

   I have java chassis SDK based `serviceA` talks to mesher acting as sidecar 
proxy for the python based `serviceB`.
   When I call serviceB operations via mesher with restclient like this
   
   ```
 RestTemplate restTemplate = RestTemplateBuilder.create();
String result =

restTemplate.getForObject("cse://testApp:shippingservice/shippingservice/bmi?height={height}&weight={weight}"
, null, 
String.class,request.getHeight(),request.getWeight());
   
   ```
   
   I am always ended up in `Message Not Found` Error.
   
   
   Then I realised that mesher would not know about the schema/operations 
supported by the sidecar main microservice which it proxies.
   
   So the question is how to register the schema in mesher with the operations 
supported in the microservice in `serviceB`
   I have tried creating schema `yaml` file and put it under `mesher/conf` 
folder. But it does not work. The schemas are not getting uploaded or 
registered in the service center.
   
   Please suggest how to make intercommunication from serviceA to serviceB 
through mesher?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] shri-arunraj opened a new issue, #159: Where is the code for mesher side car injector?

2023-03-02 Thread via GitHub


shri-arunraj opened a new issue, #159:
URL: https://github.com/apache/servicecomb-mesher/issues/159

   I see the links in the mesher documentation points to dead links.
   
   Can you please share the side car injector links?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] shri-arunraj commented on issue #158: How to register schema in mesher to make intercalls from other microservices.

2023-03-02 Thread via GitHub


shri-arunraj commented on issue #158:
URL: 
https://github.com/apache/servicecomb-mesher/issues/158#issuecomment-1451923856

   @tianxiaoliang Can you help on this issue? 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] lvsaint opened a new issue, #160: Does Mesher stop evolving?

2023-04-12 Thread via GitHub


lvsaint opened a new issue, #160:
URL: https://github.com/apache/servicecomb-mesher/issues/160

   Mesher项目不演进了吗?


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] zhufeizzz opened a new issue, #161: Mesher无法支持动态判断服务端是否开启SSL

2023-06-15 Thread via GitHub


zhufeizzz opened a new issue, #161:
URL: https://github.com/apache/servicecomb-mesher/issues/161

   Mesher不支持动态判断服务端是否开启SSL,只能在配置文件中写死协议类型,也就是说全系统必须统一为HTTP或HTTPS。
   
   具体信息参考此issue
   [#382](https://github.com/apache/servicecomb-java-chassis/issues/3820)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[GitHub] [servicecomb-mesher] dependabot[bot] opened a new pull request, #162: Bump google.golang.org/grpc from 1.27.0 to 1.53.0

2023-07-05 Thread via GitHub


dependabot[bot] opened a new pull request, #162:
URL: https://github.com/apache/servicecomb-mesher/pull/162

   Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.27.0 
to 1.53.0.
   
   Release notes
   Sourced from https://github.com/grpc/grpc-go/releases";>google.golang.org/grpc's 
releases.
   
   Release 1.53.0
   API Changes
   
   balancer: support injection of per-call metadata from LB policies (https://redirect.github.com/grpc/grpc-go/issues/5853";>#5853)
   resolver: remove deprecated field resolver.Target.Endpoint 
and replace with resolver.Target.Endpoint() (https://redirect.github.com/grpc/grpc-go/issues/5852";>#5852)
   
   Special Thanks: https://github.com/kylejb";>@​kylejb
   
   
   
   New Features
   
   xds/ringhash: introduce GRPC_RING_HASH_CAP environment 
variable to override the maximum ring size. (https://redirect.github.com/grpc/grpc-go/issues/5884";>#5884)
   rls: propagate headers received in RLS response to backends (https://redirect.github.com/grpc/grpc-go/issues/5883";>#5883)
   
   Bug Fixes
   
   transport: drain client transport when streamID approaches MaxStreamID 
(https://redirect.github.com/grpc/grpc-go/issues/5889";>#5889)
   server: after GracefulStop, ensure connections are closed when final RPC 
completes (https://redirect.github.com/grpc/grpc-go/issues/5968";>#5968)
   server: fix a few issues where grpc server uses RST_STREAM for 
non-HTTP/2 errors (https://redirect.github.com/grpc/grpc-go/issues/5893";>#5893)
   xdsclient: fix race which can happen when multiple load reporting calls 
are made at the same time. (https://redirect.github.com/grpc/grpc-go/issues/5927";>#5927)
   rls: fix a data race involving the LRU cache (https://redirect.github.com/grpc/grpc-go/issues/5925";>#5925)
   xds: fix panic involving double close of channel in xDS transport (https://redirect.github.com/grpc/grpc-go/issues/5959";>#5959)
   gcp/observability: update method name validation (https://redirect.github.com/grpc/grpc-go/issues/5951";>#5951)
   
   Documentation
   
   credentials/oauth: mark NewOauthAccess as deprecated (https://redirect.github.com/grpc/grpc-go/issues/5882";>#5882)
   
   Special Thanks: https://github.com/buzzsurfr";>@​buzzsurfr
   
   
   
   Release 1.52.3
   Bug Fixes
   
   Fix user-agent version
   
   Release 1.52.2
   Bug Fixes
   
   xds: fix panic involving double close of channel in xDS transport (https://redirect.github.com/grpc/grpc-go/issues/5959";>#5959)
   
   Release 1.52.1
   Bug Fixes
   
   grpclb: rename grpclbstate package back to state (https://redirect.github.com/grpc/grpc-go/issues/5963";>#5963)
   
   Release 1.52.0
   New Features
   
   xdsclient: log node ID with verbosity INFO (https://redirect.github.com/grpc/grpc-go/issues/5860";>#5860)
   ringhash: impose cap on max_ring_size to reduce possibility 
of OOMs (https://redirect.github.com/grpc/grpc-go/issues/5801";>#5801)
   
   Behavior Changes
   
   
   ... (truncated)
   
   
   Commits
   
   https://github.com/grpc/grpc-go/commit/dba26e15a07f43875ccf806a2dd6cbcbc1c12eab";>dba26e1
 Change version to 1.53.0 (https://redirect.github.com/grpc/grpc-go/issues/5983";>#5983)
   https://github.com/grpc/grpc-go/commit/2a1e9348ff7b5d9f4b5039e84e6c9873b5b3e26e";>2a1e934
 server: after GracefulStop, ensure connections are closed when final RPC 
comp...
   https://github.com/grpc/grpc-go/commit/e2d69aa076dd070e3668784c4dc8bcf7131b3f67";>e2d69aa
 tests: fix spelling of variable (https://redirect.github.com/grpc/grpc-go/issues/5966";>#5966)
   https://github.com/grpc/grpc-go/commit/a6376c9893f56fc3819bee9ef5d71f55cc2d38dd";>a6376c9
 xds/resolver: cleanup tests to use real xDS client 3/n (https://redirect.github.com/grpc/grpc-go/issues/5953";>#5953)
   https://github.com/grpc/grpc-go/commit/bf8fc46fa6eb913e4ed0f6dee6c6a7b75e85fbf0";>bf8fc46
 xds/resolver: cleanup tests to use real xDS client 5/n (https://redirect.github.com/grpc/grpc-go/issues/5955";>#5955)
   https://github.com/grpc/grpc-go/commit/3930549b38c0fc4cd94a95efccf7cef5f90515fd";>3930549
 resolver: replace resolver.Target.Endpoint field with Endpoint() method (https://redirect.github.com/grpc/grpc-go/issues/5852";>#5852)
   https://github.com/grpc/grpc-go/commit/894816c487f8dd48fc971c45a7c5baa4b86ef7de";>894816c
 grpclb: rename grpclbstate package back to state (https://redirect.github.com/grpc/grpc-go/issues/5962";>#5962)
   https://github.com/grpc/grpc-go/commit/e5a0237a46a5f95fa571624929be10c7afebb180";>e5a0237
 encoding: fix duplicate compressor names (https://redirect.github.com/grpc/grpc-go/issues/5958";>#5958)
   https://github.com/grpc/grpc-go/commit/4adb2a7a00d8b62df5ea34d520fe3ca13bffd31a";>4adb2a7
 xds/resolver: cleanup tests to use real xDS client 2/n (https://redirect.github.com/grpc/grpc-go/issues/5952";>#5952)
   https://github.com/grpc/grpc-go/commit/52a8392f374b8cd60e176b67925a7f8c1605d014";>52a8392
 gcp/observability: update method name validation (https://redirect.github.com/grpc/grpc-go/issu

[I] Mesher后续是否还有升级计划? [servicecomb-mesher]

2023-11-01 Thread via GitHub


yanghao605 opened a new issue, #163:
URL: https://github.com/apache/servicecomb-mesher/issues/163

   mesher当前社区版本最新1.7.0,后续社区是否有升级计划?
   这个版本再往后会超出软件使用的生命周期,影响下期选型
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Mesher无法支持动态判断服务端是否开启SSL [servicecomb-mesher]

2024-02-21 Thread via GitHub


yanghao605 commented on issue #161:
URL: 
https://github.com/apache/servicecomb-mesher/issues/161#issuecomment-1956208010

   > Mesher不支持动态判断服务端是否开启SSL,只能在配置文件中写死协议类型,也就是说全系统必须统一为HTTP或HTTPS。
   > 
   > 具体信息参考此issue 
[#382](https://github.com/apache/servicecomb-java-chassis/issues/3820)
   不太理解你的意思,Mesher作为消费端时,是可以调用Http或者Https服务的
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Mesher在转发请求时将header中的Connection移除了,这个是为什么 [servicecomb-mesher]

2024-02-21 Thread via GitHub


yanghao605 closed issue #164: Mesher在转发请求时将header中的Connection移除了,这个是为什么
URL: https://github.com/apache/servicecomb-mesher/issues/164


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [I] Mesher后续是否还有升级计划? [servicecomb-mesher]

2024-02-26 Thread via GitHub


yanghao605 closed issue #163: Mesher后续是否还有升级计划?
URL: https://github.com/apache/servicecomb-mesher/issues/163


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] bump client_golang and client_model version [servicecomb-mesher]

2024-03-03 Thread via GitHub


yanghao605 opened a new pull request, #165:
URL: https://github.com/apache/servicecomb-mesher/pull/165

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] bump client_golang and client_model version [servicecomb-mesher]

2024-03-09 Thread via GitHub


yanghao605 opened a new pull request, #166:
URL: https://github.com/apache/servicecomb-mesher/pull/166

   bump client_golang and client_model version


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] bump client_golang and client_model version [servicecomb-mesher]

2024-03-09 Thread via GitHub


yanghao605 closed pull request #165: bump client_golang and client_model version
URL: https://github.com/apache/servicecomb-mesher/pull/165


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] bump client_golang and client_model version [servicecomb-mesher]

2024-03-09 Thread via GitHub


yanghao605 merged PR #166:
URL: https://github.com/apache/servicecomb-mesher/pull/166


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] bug fix, get service ports from env [servicecomb-mesher]

2024-03-09 Thread via GitHub


yanghao605 opened a new pull request, #167:
URL: https://github.com/apache/servicecomb-mesher/pull/167

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



Re: [PR] [#119] bug fix, get service ports from env [servicecomb-mesher]

2024-03-09 Thread via GitHub


yanghao605 merged PR #167:
URL: https://github.com/apache/servicecomb-mesher/pull/167


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



[PR] sidecar模式支持sse [servicecomb-mesher]

2025-09-11 Thread via GitHub


hwzhu-hoop opened a new pull request, #171:
URL: https://github.com/apache/servicecomb-mesher/pull/171

   (no comment)


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@servicecomb.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org