Re: A question about ACID guarantees Saga provides

2018-03-13 Thread Daniel Qian
Hi Willem Jiang, thanks for your reply. I'd like to help listing a FAQ for this project, but for now, I can only provide Qs not As. Here is my Qs (sorry written in Chinese to avoid poor english obscure the meaning): 1. Saga的执行是同步的还是异步的?发起Saga之后,是等所有Sub-transaction都完成才返回,还是立即返回? 2.

[GitHub] coveralls commented on issue #584: [SCB-382] upgrade io.fabric8 docker-maven-plugin version and fix depends-on setting

2018-03-13 Thread GitBox
coveralls commented on issue #584: [SCB-382] upgrade io.fabric8 docker-maven-plugin version and fix depends-on setting URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/584#issuecomment-372017538 [![Coverage

[GitHub] codecov-io commented on issue #304: SCB-391 SC does not rotate log file

2018-03-13 Thread GitBox
codecov-io commented on issue #304: SCB-391 SC does not rotate log file URL: https://github.com/apache/incubator-servicecomb-service-center/pull/304#issuecomment-372233639 # [Codecov](https://codecov.io/gh/apache/incubator-servicecomb-service-center/pull/304?src=pr=h1) Report >

[GitHub] coveralls commented on issue #304: SCB-391 SC does not rotate log file

2018-03-13 Thread GitBox
coveralls commented on issue #304: SCB-391 SC does not rotate log file URL: https://github.com/apache/incubator-servicecomb-service-center/pull/304#issuecomment-372233609 [![Coverage Status](https://coveralls.io/builds/15944309/badge)](https://coveralls.io/builds/15944309)

[GitHub] weichao666 commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment)

2018-03-13 Thread GitBox
weichao666 commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment) URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/591#issuecomment-372562823

[GitHub] weichao666 opened a new pull request #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment)

2018-03-13 Thread GitBox
weichao666 opened a new pull request #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment) URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/591 ?evops stage(environment) Follow this checklist to help us incorporate

[GitHub] coveralls commented on issue #151: SCB-395 add guides to build executable files

2018-03-13 Thread GitBox
coveralls commented on issue #151: SCB-395 add guides to build executable files URL: https://github.com/apache/incubator-servicecomb-saga/pull/151#issuecomment-372581975 [![Coverage Status](https://coveralls.io/builds/15944648/badge)](https://coveralls.io/builds/15944648)

[GitHub] coveralls commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment)

2018-03-13 Thread GitBox
coveralls commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment) URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/591#issuecomment-372568005 [![Coverage

[GitHub] WillemJiang closed pull request #584: [SCB-382] upgrade io.fabric8 docker-maven-plugin version and fix depends-on setting

2018-03-13 Thread GitBox
WillemJiang closed pull request #584: [SCB-382] upgrade io.fabric8 docker-maven-plugin version and fix depends-on setting URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/584 This is a PR merged from a forked repository. As GitHub hides the original diff on merge,

[GitHub] weichao666 commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment)

2018-03-13 Thread GitBox
weichao666 commented on issue #591: [SCB-396] java-sdk needs to distinguish the instance belongs to the devops stage(environment) URL: https://github.com/apache/incubator-servicecomb-java-chassis/pull/591#issuecomment-372561817 sdk support registers service environment according to

[GitHub] coveralls commented on issue #152: SCB-395 remove redudant lines

2018-03-13 Thread GitBox
coveralls commented on issue #152: SCB-395 remove redudant lines URL: https://github.com/apache/incubator-servicecomb-saga/pull/152#issuecomment-372593618 [![Coverage Status](https://coveralls.io/builds/15945283/badge)](https://coveralls.io/builds/15945283) Coverage increased

[GitHub] WillemJiang commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure

2018-03-13 Thread GitBox
WillemJiang commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure URL: https://github.com/apache/incubator-servicecomb-saga/pull/138#discussion_r174074224 ## File path:

[GitHub] eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure

2018-03-13 Thread GitBox
eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure URL: https://github.com/apache/incubator-servicecomb-saga/pull/138#discussion_r174047823 ## File path:

[GitHub] coveralls commented on issue #138: [WIP] SCB-224 retry sub-transaction on failure

2018-03-13 Thread GitBox
coveralls commented on issue #138: [WIP] SCB-224 retry sub-transaction on failure URL: https://github.com/apache/incubator-servicecomb-saga/pull/138#issuecomment-368816986 [![Coverage Status](https://coveralls.io/builds/15946765/badge)](https://coveralls.io/builds/15946765)

[GitHub] WillemJiang closed pull request #41: [SCB-210] update document for apollo configuration item

2018-03-13 Thread GitBox
WillemJiang closed pull request #41: [SCB-210] update document for apollo configuration item URL: https://github.com/apache/incubator-servicecomb-website/pull/41 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake

[GitHub] WillemJiang closed pull request #151: SCB-395 add guides to build executable files

2018-03-13 Thread GitBox
WillemJiang closed pull request #151: SCB-395 add guides to build executable files URL: https://github.com/apache/incubator-servicecomb-saga/pull/151 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[GitHub] eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure

2018-03-13 Thread GitBox
eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure URL: https://github.com/apache/incubator-servicecomb-saga/pull/138#discussion_r174075643 ## File path:

[GitHub] eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure

2018-03-13 Thread GitBox
eric-lee-ltk commented on a change in pull request #138: [WIP] SCB-224 retry sub-transaction on failure URL: https://github.com/apache/incubator-servicecomb-saga/pull/138#discussion_r174047412 ## File path:

[GitHub] WillemJiang closed pull request #152: SCB-395 remove redudant lines

2018-03-13 Thread GitBox
WillemJiang closed pull request #152: SCB-395 remove redudant lines URL: https://github.com/apache/incubator-servicecomb-saga/pull/152 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

Re: servicecomb-saga的saga-demo问题

2018-03-13 Thread Willem Jiang
从你的描述上来,你应该是没有在 正确的目录下面启动 alpha server。 编译完代码之后,你可以在 /incubator-servicecomb-saga/alpha/alpha-server/target/saga 找到 alpha-server-xxx-exec.jar 还有就是建议你按照ReadMe的指示用docker compose来运行,后续我们会提供单独使用Java命令运行指示。 Please filled a JIRA[1] for it let the user run the demo without using docker compose.

servicecomb-saga的saga-demo问题

2018-03-13 Thread 叶祖锋
hi: 下了https://github.com/apache/incubator-servicecomb-saga源码,在本地通过mvn clean install编译成功。 在执行java -Dspring.profiles.active=prd -D"spring.datasource.url=jdbc:postgresql://ip:5432/saga?useSSL=false" -jar alpha-server-0.1.0.jar时提示“alpha-server-0.1.0.jar中没有主清单属性”。

Re: servicecomb-saga的saga-demo问题

2018-03-13 Thread Eric Lee
Hi, 叶祖锋 Seems like you used the wrong jar file. The executable jar file should be ` alpha/alpha-server/target/saga/alpha-server-0.1.0-exec.jar` according to the user guide [1]. Besides, it seems there is port conflict in your log. Can you double check if other apps is using the exact port of

[GitHub] coveralls commented on issue #153: SCB-395 add guides to run demo without docker compose

2018-03-13 Thread GitBox
coveralls commented on issue #153: SCB-395 add guides to run demo without docker compose URL: https://github.com/apache/incubator-servicecomb-saga/pull/153#issuecomment-372895796 [![Coverage Status](https://coveralls.io/builds/15963246/badge)](https://coveralls.io/builds/15963246)

Request the Permission using Apache ServiceCom(incubating) name in our Meetup

2018-03-13 Thread Willem Jiang
Hi ASF Marketing & Publicity, We will hold a meetup in Beijing, China at March 31, 2018, by using Apache ServiceComb(incubating) as part of the event name to build up the Apache ServiceComb community. I want through the document of small-events tips[1], which said we need approve from the PMC.

Re: Fw: Request the Permission using Apache ServiceCom(incubating) name in our Meetup

2018-03-13 Thread Sally Khudairi
Hello Willem --thank you for your message. There are no issues with your use of the podling name to help promote your event and help build your community as long as the naming is along the lines of "Apache ServiceComb (incubating) MeetUp". If you can please confirm the name of your event, we'd

Re: Fw: Request the Permission using Apache ServiceCom(incubating) name in our Meetup

2018-03-13 Thread Willem Jiang
Hi Sally, Actually the meetup is holded by two community, one is "Apache ServiceComb(incubating)", the other is "树人云" a startup cloud company provides PaaS platform. And we use "Apache ServiceComb(incubating) && 树人云 ” as the meetup name. BTW, We also invited "Apache Skywalking(incubating)" as a

Re: Fw: Fw: Request the Permission using Apache ServiceCom(incubating) namein our Meetup

2018-03-13 Thread Sally Khudairi
Thank you for notifying us, Sheng. As with Apache ServiceComb, please be sure to send us the Apache SkyWalking naming/promotions when available. Also, I'm not sure if your Incubator mentor has mentioned it to you, but creators/inventors of projects that are now at the ASF may be referred to as

Re: Fw: Request the Permission using Apache ServiceCom(incubating) namein our Meetup

2018-03-13 Thread ???? Sheng Wu
Hi Sally Apache SkyWalking (incubating) project will join the meeting too. We will follow the rule. -- Sheng Wu Apache SkyWalking creator and PPMC member -- Original -- From: "Sally Khudairi"; Date: Wed, Mar 14,

[GitHub] eric-lee-ltk opened a new pull request #153: SCB-395 add guides to run demo without docker compose

2018-03-13 Thread GitBox
eric-lee-ltk opened a new pull request #153: SCB-395 add guides to run demo without docker compose URL: https://github.com/apache/incubator-servicecomb-saga/pull/153 Signed-off-by: Eric Lee Follow this checklist to help us incorporate your contribution quickly

Re: Fw: Request the Permission using Apache ServiceCom(incubating) name in our Meetup

2018-03-13 Thread Willem Jiang
Hi Sally, As 树人云 doesn't use Apache ServiceComb to build their PaaS product and we both want to build up the community about building microservice. Can we change the event name to " Building Microservice Meetup presented by Apache ServiceComb(incubating) && 树人云"? Willem Jiang Blog:

Re: Fw: Request the Permission using Apache ServiceCom(incubating) name in our Meetup

2018-03-13 Thread Sally Khudairi
Thank you, Willem. As the ASF is vendor-neutral, you may state the event as "Apache ServiceComb (incubating) MeetUp presented by 树人云" but they cannot be combined together. "Presented" is just a suggestion: it can be "hosted", "supported", or other such words. I appreciate that you are having

Re: A question about ACID guarantees Saga provides

2018-03-13 Thread Daniel Qian
Thanks a lot, Willem Jiang, 关于Q7我举个例子来说明我的意思: App version 1.0 里的Saga是这样的:call methodA, call methodB App version 2.0 里的代码是这样的:call methodA, call methodC 把App从1.0 升级到 2.0必定需要将原1.0的App进程停止,然后启动2.0的App进程。 在停止1.0的App进程的时候,可能会出现Saga只执行了一半。 那么启动2.0的App进程之后,会出现以下哪种情况: 1. 1.0 App的未执行完成的Saga永远保持未完成状态 2.

[GitHub] liubao68 commented on issue #592: 【请关注】服务消费者调用服务提供者接口时,目前缺少接口级别或者动态的超时设置能力,无法满足服务接口差异化诉求

2018-03-13 Thread GitBox
liubao68 commented on issue #592: 【请关注】服务消费者调用服务提供者接口时,目前缺少接口级别或者动态的超时设置能力,无法满足服务接口差异化诉求 URL: https://github.com/apache/incubator-servicecomb-java-chassis/issues/592#issuecomment-372874403 这个问题更像是一个复杂业务场景的解决方案。有些问题时需要深入讨论的。结合上面的描述,个人的一些建议: 1.

[GitHub] liubao68 commented on issue #576: 业务代码使用RegistryUtils方法报空指针

2018-03-13 Thread GitBox
liubao68 commented on issue #576: 业务代码使用RegistryUtils方法报空指针 URL: https://github.com/apache/incubator-servicecomb-java-chassis/issues/576#issuecomment-372874736 This is not a valid case. Make sure everything is ready before use it .