Re: [discuss] some log question
Ok, i am willing to try, have any tips for configuring the log level via environment variable ? If not, I will try PR after I have conceived it correctly. If I miss something, please remind me. Thanks! - lan.liang On 10/25/2019 09:03，Yihua Cui wrote： SC log in DEBUG level by default, I suggest support for configuring the log level via environment variable. Can you raise a PR to solve it? On 2019/10/23 05:21:37, yp wrote: Hey guys: The are a lot of duplicate logs after starting servicecomb-sc, Some like : ** 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[244.81µs]finish to cache key /cse-sr/ms/dep-rules/, 2 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.643µs]finish to cache key /cse-sr/domains/, 1 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.243µs]finish to cache key /cse-sr/ms/tags/, 0 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[187.147µs]finish to cache key /cse-sr/inst/leases/, 1 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[166.848µs]finish to cache key /cse-sr/ms/rules/, 0 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[277.301µs]finish to cache key /cse-sr/ms/alias/, 1 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.613854ms]finish to cache key /cse-sr/ms/schema-sum/, 1 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[165.661µs]finish to cache key /cse-pact/version/, 0 items, rev: 28 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[229.101µs]finish to cache key /cse-sr/inst/files/, 1 items, rev: 28 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[129.673µs]finish to cache key /cse-pact/latest/, 0 items, rev: 28 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[172.488µs]finish to cache key /cse-sr/ms/indexes/, 3 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.082668ms]finish to cache key /cse-sr/projects/, 1 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[838.669µs]finish to cache key /cse-sr/ms/rule-indexes/, 0 items, rev: 28 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.386158ms]finish to cache key /cse-sr/ms/dep-queue/, 0 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[484.118µs]finish to cache key /cse-pact/participant/, 0 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.9711ms]finish to cache key /cse-sr/ms/files/, 3 items, rev: 28 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.135947ms]finish to cache key /cse-pact/pact-version/, 0 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[601.773µs]finish to cache key /cse-pact/pact/, 0 items, rev: 28 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.593579ms]finish to cache key /cse-pact/pact-tag/, 0 items, rev: 28 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.548803ms]finish to cache key /cse-pact/verification/, 0 items, rev: 28 2019-10-23T13:12:19.792+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] CLEARED, map[] 2019-10-23T13:12:48.817+0800INFOservice/instance.go:323heartbeat successful, renew instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] ttl to 120. operator 2019-10-23T13:12:48.818+0800DEBUGbackend/registry.go:216update service center instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] heartbeat 2019-10-23T13:12:49.797+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] CLEARED, map[] 2019-10-23T13:13:18.820+0800INFOservice/instance.go:323heartbeat successful, renew instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] ttl to 120. operator 2019-10-23T13:13:18.820+0800DEBUGbackend/registry.go:216update service center instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] heartbeat 2019-10-23T13:13:19.798+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] CLEARED, map[] 2019-10-23T13:13:48.823+0800INFOservice/instance.go:323heartbeat successful, renew instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] ttl to 120. operator 2019-10-23T13:13:48.823+0800DEBUGbackend/registry.go:216update service center instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] heartbeat 2019-10-23T13:13:49.800+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] CLEARED, map[] ** I have't started any apps yet, Is this the expected effect? One more,why do you need to display the go file in the sc log? Is it necessary? It’s weird in my opinion. If i missed something, remind me please! Thanks! - lan.liang
Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0
Hi All, We are glad to announce that ServiceComb community has approved the Apache ServiceComb Kie version 0.1.0 release with the following results: +1 binding: 5 (Willem Jiang, yhs0092， Bin Ma，liubao，cuiyihua ) +1 non-binding: 4 (yang bo, sen sun, victor chan,alec zheng) We will release the version soon. Thanks All for your participation in this vote. Best Wishes & Regards xiaoliang tian Willem Jiang 于2019年10月25日周五 上午8:22写道： > +1. > > Checked the License and Notice files. > They are much better now. > > Willem Jiang > > Twitter: willemjiang > Weibo: 姜宁willem > > On Mon, Oct 21, 2019 at 8:38 PM Xiaoliang Tian > wrote: > > > > Hi All, > > > > This is a call for Vote to release Apache ServiceComb Kie version 0.1.0 > > > > Release Candidate : > > > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-03/ > > > > > > > > Release Tag : > > https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0 > > > > Release CommitID: 65ead3641f33c02055d4365020736d7b4cf34779 > > > > Release Notes : > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626&version=12345632 > > > > Keys to verify the Release Candidate : > > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > > > Voting will start now ( Monday, 21nd October , 2019) and will remain open > > for at-least 72 hours, Request all PMC members to give their vote. > > > > [ ] +1 Release this package as 0.1.0 > > [ ] +0 No Opinion > > [ ] -1 Do not release this package because > > > > On the behalf of ServiceComb Team > > > > > > Best Wishes & Regards >
Re: [discuss] some log question
SC log in DEBUG level by default, I suggest support for configuring the log level via environment variable. Can you raise a PR to solve it? On 2019/10/23 05:21:37, yp wrote: > Hey guys: > > The are a lot of duplicate logs after starting servicecomb-sc, > > > Some like : > > > ** > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[244.81µs]finish to > cache key /cse-sr/ms/dep-rules/, 2 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.643µs]finish to > cache key /cse-sr/domains/, 1 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[231.243µs]finish to > cache key /cse-sr/ms/tags/, 0 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[187.147µs]finish to > cache key /cse-sr/inst/leases/, 1 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[166.848µs]finish to > cache key /cse-sr/ms/rules/, 0 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[277.301µs]finish to > cache key /cse-sr/ms/alias/, 1 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.613854ms]finish to > cache key /cse-sr/ms/schema-sum/, 1 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[165.661µs]finish to > cache key /cse-pact/version/, 0 items, rev: 28 > 2019-10-23T13:12:18.807+0800DEBUGetcd/cacher_kv.go:83[229.101µs]finish to > cache key /cse-sr/inst/files/, 1 items, rev: 28 > 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[129.673µs]finish to > cache key /cse-pact/latest/, 0 items, rev: 28 > 2019-10-23T13:12:18.808+0800DEBUGetcd/cacher_kv.go:83[172.488µs]finish to > cache key /cse-sr/ms/indexes/, 3 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.082668ms]finish to > cache key /cse-sr/projects/, 1 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[838.669µs]finish to > cache key /cse-sr/ms/rule-indexes/, 0 items, rev: 28 > 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.386158ms]finish to > cache key /cse-sr/ms/dep-queue/, 0 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[484.118µs]finish to > cache key /cse-pact/participant/, 0 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.9711ms]finish to > cache key /cse-sr/ms/files/, 3 items, rev: 28 > 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.135947ms]finish to > cache key /cse-pact/pact-version/, 0 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[601.773µs]finish to > cache key /cse-pact/pact/, 0 items, rev: 28 > 2019-10-23T13:12:18.810+0800DEBUGetcd/cacher_kv.go:83[1.593579ms]finish to > cache key /cse-pact/pact-tag/, 0 items, rev: 28 > 2019-10-23T13:12:18.811+0800DEBUGetcd/cacher_kv.go:83[2.548803ms]finish to > cache key /cse-pact/verification/, 0 items, rev: 28 > 2019-10-23T13:12:19.792+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] > CLEARED, map[] > 2019-10-23T13:12:48.817+0800INFOservice/instance.go:323heartbeat successful, > renew > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > ttl to 120. operator > 2019-10-23T13:12:48.818+0800DEBUGbackend/registry.go:216update service center > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > heartbeat > 2019-10-23T13:12:49.797+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] > CLEARED, map[] > 2019-10-23T13:13:18.820+0800INFOservice/instance.go:323heartbeat successful, > renew > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > ttl to 120. operator > 2019-10-23T13:13:18.820+0800DEBUGbackend/registry.go:216update service center > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > heartbeat > 2019-10-23T13:13:19.798+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] > CLEARED, map[] > 2019-10-23T13:13:48.823+0800INFOservice/instance.go:323heartbeat successful, > renew > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > ttl to 120. operator > 2019-10-23T13:13:48.823+0800DEBUGbackend/registry.go:216update service center > instance[7062417bf9ebd4c646bb23059003cea42180894a/24e02f56f4d611e9a30f8c8590750471] > heartbeat > 2019-10-23T13:13:49.800+0800DEBUGalarm/service.go:85alarm[BackendConnectionRefuse] > CLEARED, map[] > ** > > > I have't started any apps yet, Is this the expected effect? > > > One more,why do you need to display the go file in the sc log? Is it > necessary? > > > It’s weird in my opinion. > > > If i missed something, remind me please! Thanks! > > > - lan.liang > >
Re: [VOTE] Release Apache ServiceComb Kie version 0.1.0
+1. Checked the License and Notice files. They are much better now. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Mon, Oct 21, 2019 at 8:38 PM Xiaoliang Tian wrote: > > Hi All, > > This is a call for Vote to release Apache ServiceComb Kie version 0.1.0 > > Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/servicecomb-kie/0.1.0/rc-03/ > > > > Release Tag : > https://github.com/apache/servicecomb-kie/releases/tag/v0.1.0 > > Release CommitID: 65ead3641f33c02055d4365020736d7b4cf34779 > > Release Notes : > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12321626&version=12345632 > > Keys to verify the Release Candidate : > https://dist.apache.org/repos/dist/dev/servicecomb/KEYS > > Voting will start now ( Monday, 21nd October , 2019) and will remain open > for at-least 72 hours, Request all PMC members to give their vote. > > [ ] +1 Release this package as 0.1.0 > [ ] +0 No Opinion > [ ] -1 Do not release this package because > > On the behalf of ServiceComb Team > > > Best Wishes & Regards
Re: [DISCUSSION] Environment in infomation log not correct in servicecomb-java-chassis
+1 to keep the log format consistent. Willem Jiang Twitter: willemjiang Weibo: 姜宁willem On Fri, Oct 18, 2019 at 6:26 PM Ang Li wrote: > > Hi team, > > > In servicecomb-java-chassis master branch, log will contains service > information as following: > > > service center: > config center: ... > ... > Environment: ... > ... > > > But, when the environment in microservice.yaml is set as "development", the > log will still print "Environment: production". It seems that the related > feature works, just log not correct. > > > Also, the format of names is not the same now, some are lowercase, some are > initial capitiaization and others are camel-case. I think keep the format > consistent is better. > > > > > Ang Li
Re: Swagger Codegen
Sorry,I',m not free on this Friday, how about this Saturday(Beijing time)? Wishes & Regards --- Mabin William Cheng 于2019年10月24日周四 上午8:14写道： > Are you free for a quick chat (IM) tomorrow (Friday)? > > My timezone is +0800. > > We can use Google Hangout or other IM channels you prefer (e.g. WeChat). > > Best regards, > William > > On Wed, 23 Oct 2019 at 19:59, Bin Ma wrote: > >> Hi William Cheng, >> >> Thanks for your interest in the servicecomb-toolkit project, the >> codegen of the servicecomb-toolkit project implements the microservices >> code template[1] base on ServiceComb, and I learned that the >> OpenAPITools/openapi-generator project [2] also provides a >> collection of code templates, so I think maybe we can form some >> cooperation >> on this, I'd like to hear from you, looking forward to your reply. >> >> Thanks: ) >> >> [1] >> https://github.com/apache/servicecomb-toolkit/tree/master/codegen/src/main/resources/ServiceComb >> >> [2] >> https://github.com/OpenAPITools/openapi-generator/tree/master/modules/openapi-generator/src/main/resources >> >> Wishes & Regards >> --- >> Mabin >> >> >> >> sen sun 于2019年10月23日周三 下午3:34写道： >> >>> Hi William, >>> >>> I have read your email in detail. I have learned about the relationship >>> between openapi-generator( >>> https://github.com/OpenAPITools/openapi-generator) >>> and swagger-codegen(https://github.com/swagger-api/swagger-codegen) . >>> When >>> upgrading to openapi v3, we used openapi-generator in our project( >>> >>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L347 >>> ). >>> There are no hard-to-solve problems in the current use. If there is a >>> problem, I will give feedback in time. Thanks >>> >>> Willem Jiang 于2019年10月21日周一 下午5:06写道： >>> >>> > Hi William， >>> > >>> > Thanks for your information. It's good to know there are some new >>> > features of OpenAPI Generator. >>> > Current we are leverage OpenAPI to do the contract first web service >>> > development, and we just upgrade to use OpenAPI V3 in the toolkit. >>> > I'm not the writer of toolkit, so I just forward the mail to the >>> > dev@servicecomb, maybe Sun LiShen can answer your questions. >>> > >>> > Willem Jiang >>> > >>> > Twitter: willemjiang >>> > Weibo: 姜宁willem >>> > >>> > On Mon, Oct 21, 2019 at 12:35 AM William Cheng >>> > wrote: >>> > > >>> > > Hi, >>> > > >>> > > Understood that you're busy. I've an important news to share with >>> you: >>> > > >>> > > In May 2018, myself and other top contributors (40+) have decided to >>> > fork Swagger Codegen to maintain a community-driven version called >>> "OpenAPI >>> > Generator" (https://openapi-generator.tech), which supports both >>> > OpenAPI/Swagger spec v2 and v3. >>> > > >>> > > For the reasons behind the fork, please refer to the Q&A: >>> > >>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/qna.md >>> . >>> > For migration, please refer to >>> > >>> https://github.com/OpenAPITools/openapi-generator/blob/master/docs/migration-from-swagger-codegen.md >>> > > >>> > > 2 weeks ago we released OpenAPI Generator v4.1.3 with 4 new >>> generators - >>> > https://twitter.com/oas_generator/status/1180123829626003456. Please >>> > check it out and let us know if you've any feedback or questions. >>> > > >>> > > Best regards, >>> > > William >>> > > https://github.com/wing328 >>> > > >>> > > On Fri, 18 Oct 2019 at 02:14, William Cheng >>> wrote: >>> > >> >>> > >> Hi Willem, >>> > >> >>> > >> Sorry for reaching out to you directly. I saw you using Swagger >>> > Codegen: >>> > >>> https://github.com/apache/servicecomb-toolkit/blob/fa55b53ae66e5e6323dba88339b1eb0014003c15/toolkit-distribution/src/release/LICENSE#L357 >>> > >> >>> > >> I'm the top contributor to Swagger Codegen. May I know how's your >>> > experience with Swagger Codegen so far? Did you find it easy to use and >>> > customize? >>> > >> >>> > >> Best regards, >>> > >> William >>> > >> https://github.com/wing328 >>> > >>> >>
