Re: [ANNOUNCE] new PPMC: liling
Congratulations. [email protected] From: Ming Wen Date: 2020-03-06 16:02 To: dev Subject: [ANNOUNCE] new PPMC: liling hello, community, The Project Management Committee(PMC) of Apache APISIX has vote passed and invited liling to be a PPMC. We are pleased to announce that he has accepted. Congratulations liling:) Thanks, Ming Wen, Apache APISIX Twitter: _WenMing
Re: [ANNOUNCE] new committer: spacewander
Congratulations. [email protected] From: Ming Wen Date: 2020-03-16 19:47 To: dev Subject: [ANNOUNCE] new committer: spacewander hello, community, The Project Management Committee(PMC) of Apache APISIX has vote passed and invited spacewander to be a committer. We are pleased to announce that he has accepted. Congratulations and welcome spacewander. Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing
Re: Re: [ANNOUNCE] New committer: Akayeshmantha
Congratulations. [email protected] From: Nirojan Selvanathan Date: 2020-03-23 20:04 To: dev Subject: Re: [ANNOUNCE] New committer: Akayeshmantha Congrats! On Mon, Mar 23, 2020 at 11:56 AM YuanSheng Wang wrote: > Congratulations Akayeshmantha ^_^ > > On Mon, Mar 23, 2020 at 3:45 PM Ming Wen wrote: > > > hello, community, > > > > The Project Management Committee(PMC) of Apache APISIX has vote passed > and > > invited Akayeshmantha to be a committer. We are pleased to announce that > he > > has accepted. > > > > Congratulations Akayeshmantha and welcome to join us. > > > > Thanks, > > Ming Wen, Apache APISIX & Apache SkyWalking > > Twitter: _WenMing > > > > > -- > *MembPhis* > My github: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix > -- Best Regards, S.Nirojan
Re: Re: Improve the website of Apache APISIX
that's cool. [email protected] From: Ayeshmantha Perera Date: 2020-03-31 00:46 To: dev Subject: Re: Improve the website of Apache APISIX Hi All It looks great.Nice work zhiyuan Regards Ayesh On Mon 30. Mar 2020 at 16:34, Ming Wen wrote: > Hi, community, > zhiyuan updated the website of Apache APISIX[1] to made it obvious is an > ASF project. > Please take a look, and welcome feedback. > > [1] http://apisix.apache.org/ > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > YuanSheng Wang 于2020年3月27日周五 上午8:54写道： > > > For example, we need to update ASF logo. See [1] for the latest ASF > logos. > > > > [1] https://www.apache.org/foundation/press/kit/ > > > > > > On Fri, Mar 27, 2020 at 8:48 AM YuanSheng Wang > > wrote: > > > > > > I am reading it and learned some new issues, we can copy and fix them > > directly. > > > > > > On Fri, Mar 27, 2020 at 8:43 AM Ming Wen wrote: > > > > > > > > Hello, community, > > > > I am following Apache ShardingSphere's graduation discussions[1], > this > > is a > > > > great opportunity to learn the Apache way and help Apache APISIX deal > > with > > > > website and brand issues. > > > > > > > > I think we should improve the website of Apache APISIX to make it's > > obvious > > > > this is an ASF project, what do you think? > > > > > > > > [1] > > > > > > > https://lists.apache.org/thread.html/rc8319ca419b347c82d79b8cb5f72b20b9e6713a18f6f01dbecf26512%40%3Cgeneral.incubator.apache.org%3E > > > > > > > > Thanks, > > > > Ming Wen, Apache APISIX & Apache SkyWalking > > > > Twitter: _WenMing > > > > > > > > > > > > -- > > > MembPhis > > > My github: https://github.com/membphis > > > Apache APISIX: https://github.com/apache/incubator-apisix > > > > > > > > -- > > MembPhis > > My github: https://github.com/membphis > > Apache APISIX: https://github.com/apache/incubator-apisix > > > -- *Software Engineer* *Salzburg Research Forschungsgesellschaft * *Salzburg, Austria*
the error happend when use the healthcheck to get the status of upstrems.
I got the error when I use the healthcheck to get the status of upstrems. Has anyone ever had the same problem? Error: 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API disabled in the context of balancer_by_lua* stack traceback: [C]: in function 'sleep' /usr/local/openresty/lualib/resty/lock.lua:153: in function 'lock' /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in function 'locking_target_list' /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: in function 'new' /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function 'create_obj_fun' /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function 'lrucache_checker' /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function 'fetch_checker' /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function 'pick_server' /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function 'load_balancer' /opt/app/mecs//lua/travelsky.lua:259: in function 'http_balancer_phase' balancer_by_lua:2: in main chunk while connecting to upstream, client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: "101.5.19.15:8080" [email protected]
Re: Re: the error happend when use the healthcheck to get the status of upstrems.
Is there any way to avoid this? [email protected] From: YuanSheng Wang Date: 2020-04-01 22:43 To: [email protected] Subject: Re: the error happend when use the healthcheck to get the status of upstrems. That is a bug of lua-resty-healthcheck, here is the related issue [1]. It is not easy to fix it. [1] https://github.com/Kong/lua-resty-healthcheck/issues/36 On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> wrote: > I got the error when I use the healthcheck to get the status of upstrems. > Has anyone ever had the same problem? > > Error: > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API > disabled in the context of balancer_by_lua* > stack traceback: > [C]: in function 'sleep' > /usr/local/openresty/lualib/resty/lock.lua:153: in function 'lock' > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in > function 'locking_target_list' > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: in > function 'new' > /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function > 'create_obj_fun' > /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function > 'lrucache_checker' > /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function > 'fetch_checker' > /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function > 'pick_server' > /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function > 'load_balancer' > /opt/app/mecs//lua/travelsky.lua:259: in function > 'http_balancer_phase' > balancer_by_lua:2: in main chunk while connecting to upstream, > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: " > 101.5.19.15:8080" > > > > > [email protected] > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
Re: Re: the error happend when use the healthcheck to get the status of upstrems.
Thx. [email protected] From: YuanSheng Wang Date: 2020-04-02 11:58 To: [email protected] Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. I do not know how to fix it yet. On Wed, Apr 1, 2020 at 10:47 PM [email protected] <[email protected]> wrote: > Is there any way to avoid this? > > > > [email protected] > > From: YuanSheng Wang > Date: 2020-04-01 22:43 > To: [email protected] > Subject: Re: the error happend when use the healthcheck to get the status > of upstrems. > That is a bug of lua-resty-healthcheck, here is the related issue [1]. > > It is not easy to fix it. > > [1] https://github.com/Kong/lua-resty-healthcheck/issues/36 > > > > On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> wrote: > > > I got the error when I use the healthcheck to get the status of upstrems. > > Has anyone ever had the same problem? > > > > Error: > > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run > > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API > > disabled in the context of balancer_by_lua* > > stack traceback: > > [C]: in function 'sleep' > > /usr/local/openresty/lualib/resty/lock.lua:153: in function > 'lock' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in > > function 'locking_target_list' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: in > > function 'new' > > /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function > > 'create_obj_fun' > > /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function > > 'lrucache_checker' > > /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function > > 'fetch_checker' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function > > 'pick_server' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function > > 'load_balancer' > > /opt/app/mecs//lua/travelsky.lua:259: in function > > 'http_balancer_phase' > > balancer_by_lua:2: in main chunk while connecting to upstream, > > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: " > > 101.5.19.15:8080" > > > > > > > > > > [email protected] > > > > > -- > *MembPhis* > My github: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
Re: Re: the error happend when use the healthcheck to get the status of upstrems.
@MembPhis， thanks for your reply, I 'll use the lua-resty-healthcheck-api7 to update my scenarios. [email protected] From: [email protected] Date: 2020-04-03 09:22 To: dev Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. Thx. [email protected] From: YuanSheng Wang Date: 2020-04-02 11:58 To: [email protected] Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. I do not know how to fix it yet. On Wed, Apr 1, 2020 at 10:47 PM [email protected] <[email protected]> wrote: > Is there any way to avoid this? > > > > [email protected] > > From: YuanSheng Wang > Date: 2020-04-01 22:43 > To: [email protected] > Subject: Re: the error happend when use the healthcheck to get the status > of upstrems. > That is a bug of lua-resty-healthcheck, here is the related issue [1]. > > It is not easy to fix it. > > [1] https://github.com/Kong/lua-resty-healthcheck/issues/36 > > > > On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> wrote: > > > I got the error when I use the healthcheck to get the status of upstrems. > > Has anyone ever had the same problem? > > > > Error: > > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run > > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API > > disabled in the context of balancer_by_lua* > > stack traceback: > > [C]: in function 'sleep' > > /usr/local/openresty/lualib/resty/lock.lua:153: in function > 'lock' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in > > function 'locking_target_list' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: in > > function 'new' > > /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function > > 'create_obj_fun' > > /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function > > 'lrucache_checker' > > /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function > > 'fetch_checker' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function > > 'pick_server' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function > > 'load_balancer' > > /opt/app/mecs//lua/travelsky.lua:259: in function > > 'http_balancer_phase' > > balancer_by_lua:2: in main chunk while connecting to upstream, > > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: " > > 101.5.19.15:8080" > > > > > > > > > > [email protected] > > > > > -- > *MembPhis* > My github: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
Re: Re: [VOTE] Release Apache APISIX (Incubating) 1.2-RC1
+1 [email protected] From: Justin Mclean Date: 2020-04-13 10:12 To: dev Subject: Re: [VOTE] Release Apache APISIX (Incubating) 1.2-RC1 Hi, +1 (binding) I checked: - incubating in name - signatures and hash fine - DISCLAIMER exists - LICENSE and NOTICE all good - All source files have ASF headers - No unexpected binary files - I didn’t;t compile form source (environment not set up) Thanks, Justin
[help] how to solve the plugin's complex schema?
Hi,
I want to develop a new APISIX plug-in for my scenario, but it's schema is
more complex, the recommended way is to split it into multiple plug-ins or to
keep one?
I want to get it form the schema file instead of initializing the table in it's
file if recommend the latter.
Is there anything wrong or some risk in this way.
```
local prefix = ngx.config.prefix()
local plugin_xsd_file = prefix .. "/conf/plugin.schema.json"
local f = assert(io.open(cfg_file))
local xsd_t = json.decode(assert(f:read('*a')))
f:close()
--local myvalidator = jsonschema.generate_validator(xsd_t)
```
thx~
[email protected]
Re: [RESULT] [VOTE] Release Apache APISIX (incubating) 1.2
Congratulations. [email protected] From: agile6v Date: 2020-04-20 10:45 To: [email protected] Subject: [RESULT] [VOTE] Release Apache APISIX (incubating) 1.2 Hi all, Release vote for Release Apache APISIX (Incubating) 1.2 has PASSED and closed now. The results are as follows: 3 IPMC +1 votes: - Justin Mclean - Willem Jiang - Sheng Wu 8 +1 votes: - Ming Wen - YuanSheng Wang - Nirojan Selvanathan - JunXu Chen - Lang Wang - Li Ling - Ayeshmantha Perera - Linsir Wu Vote thread: https://lists.apache.org/thread.html/rc8ae3207f0aae16ebf655cf0350ce5f295cdc41c208e2ae5a77085f6%40%3Cdev.apisix.apache.org%3E I'm going to publish the source release of Apache APISIX (incubating) 1.2 and send ANNOUNCE later. Thank you all for making this happen! Thanks, agile6v
Re: Re: the error happend when use the healthcheck to get the status of upstrems.
@MembPhis， The timer delays adding targets, so it will get an error if use the get_target_status function to get the status of a node before the targets assigned. It's the best to use the get_target_status function by pcall, and use the default is_healthy status as result. [email protected] From: [email protected] Date: 2020-04-09 09:21 To: dev Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. @MembPhis， thanks for your reply, I 'll use the lua-resty-healthcheck-api7 to update my scenarios. [email protected] From: [email protected] Date: 2020-04-03 09:22 To: dev Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. Thx. [email protected] From: YuanSheng Wang Date: 2020-04-02 11:58 To: [email protected] Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. I do not know how to fix it yet. On Wed, Apr 1, 2020 at 10:47 PM [email protected] <[email protected]> wrote: > Is there any way to avoid this? > > > > [email protected] > > From: YuanSheng Wang > Date: 2020-04-01 22:43 > To: [email protected] > Subject: Re: the error happend when use the healthcheck to get the status > of upstrems. > That is a bug of lua-resty-healthcheck, here is the related issue [1]. > > It is not easy to fix it. > > [1] https://github.com/Kong/lua-resty-healthcheck/issues/36 > > > > On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> wrote: > > > I got the error when I use the healthcheck to get the status of upstrems. > > Has anyone ever had the same problem? > > > > Error: > > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run > > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API > > disabled in the context of balancer_by_lua* > > stack traceback: > > [C]: in function 'sleep' > > /usr/local/openresty/lualib/resty/lock.lua:153: in function > 'lock' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: in > > function 'locking_target_list' > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: in > > function 'new' > > /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function > > 'create_obj_fun' > > /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function > > 'lrucache_checker' > > /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function > > 'fetch_checker' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in function > > 'pick_server' > > /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in function > > 'load_balancer' > > /opt/app/mecs//lua/travelsky.lua:259: in function > > 'http_balancer_phase' > > balancer_by_lua:2: in main chunk while connecting to upstream, > > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: " > > 101.5.19.15:8080" > > > > > > > > > > [email protected] > > > > > -- > *MembPhis* > My github: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
Re: Re: [DISCUSS] bi-weekly online video meeting
I've watched the video, that's good. [email protected] From: Ming Wen Date: 2020-04-26 11:10 To: dev Subject: Re: [DISCUSS] bi-weekly online video meeting hello, The live broadcast was attended by over 50 people, and I spent half an hour sharing the Apache way and the development experience of Apache APISIX. I created an account for Apache APISIX at bilibili[1] and uploaded the video of this meeting. If anyone wants to upload a video of Apache APISIX, ping me and I can help upload to this channel. [1] https://space.bilibili.com/551921247 Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing hui li 于2020年4月23日周四 上午11:01写道： > We can upload the conference video to BILIBILI > BILIBILI's upload speed is very fast, and it also respect the original > creator > > YuanSheng Wang 于2020年4月21日周二 下午10:46写道： > > > Hi: > > > > Should we do video recording? > > > > Where will we upload these video content later? > > > > > > On Tue, Apr 21, 2020 at 4:59 PM hui li wrote: > > > > > hi, > > > I want to know how long the first meeting will last? Generally > speaking, > > it > > > takes at least 45 minutes to clarify an issue. Too short meeting time > or > > > too many issues are often not so effective. > > > Secondly, whether the conference platform uses Tencent conference or > > > BILIBILI live? > > > What is the theme of this video meeting? The topic is to introduce the > > new > > > features of version 1.2 and how to use it? > > > > > > Ming Wen 于2020年4月21日周二 下午4:33写道： > > > > > > > hello, > > > > Here's the info of Tencent meeting, and we will discuss the apache > way > > > and > > > > new features of Apache APISIX 1.2. > > > > > > > > This is our first online meeting and welcome everyone:) > > > > > > > > time: 2020/4/23 20:00-21:00 (BST) > > > > > > > > meeting link: > > > > https://meeting.tencent.com/s/5aNrDI62ce1b > > > > > > > > ID：779 364 680 > > > > > > > > broadcast live： > > > > https://meeting.tencent.com/l/5pyMOa34dfd9 > > > > > > > > Thanks, > > > > Ming Wen, Apache APISIX & Apache SkyWalking > > > > Twitter: _WenMing > > > > > > > > > > > > Sheng Wu 于2020年4月21日周二 上午9:38写道： > > > > > > > > > Justin Mclean 于2020年4月21日周二 上午9:34写道： > > > > > > > > > > > Hi, > > > > > > > > > > > > > `bi-weekly` means having one every 2 weeks. > > > > > > > > > > > > It can also confusingly mean twice a week. Here in Australia it > > > usually > > > > > > means twice a week and fortnightly once every two weeks,. > > > > > > > > > > > > > > > > haha, interesting. > > > > > > > > > > Sheng Wu 吴晟 > > > > > Twitter, wusheng1108 > > > > > > > > > > > > > > > > > > > > > > Justin > > > > > > > > > > > > > > > > > > -- > > *MembPhis* > > My github: https://github.com/membphis > > Apache APISIX: https://github.com/apache/incubator-apisix > > >
Re: Re: the error happend when use the healthcheck to get the status of upstrems.
In this version, the error still exists. I've opened an issue(https://github.com/Kong/lua-resty-healthcheck/issues/43) and pulled a request to fix it. I can't find the lua-resty-healthcheck-iresty lib among APISIX's repository, so I opened the issue on that. [email protected] From: YuanSheng Wang Date: 2020-04-28 14:58 To: [email protected] Subject: Re: Re: the error happend when use the healthcheck to get the status of upstrems. On Tue, Apr 28, 2020 at 2:48 PM YuanSheng Wang wrote: > > > On Thu, Apr 23, 2020 at 2:54 PM [email protected] <[email protected]> wrote: > >> @MembPhis， >> The timer delays adding targets, so it will get an error if use the >> get_target_status function to get the status of a node before the targets >> assigned. >> It's the best to use the get_target_status function by pcall, and use the >> default is_healthy status as result. >> >> > Thank you very much for your explanation. > > We have released version 1.0.1 of lua-resty-healthcheck-iresty. It should > have solved this problem. > the latest version should be 2.2.0. sorry for this. > > >> >> >> >> [email protected] >> >> From: [email protected] >> Date: 2020-04-09 09:21 >> To: dev >> Subject: Re: Re: the error happend when use the healthcheck to get the >> status of upstrems. >> @MembPhis， thanks for your reply, I 'll use the >> lua-resty-healthcheck-api7 to update my scenarios. >> >> >> >> [email protected] >> >> From: [email protected] >> Date: 2020-04-03 09:22 >> To: dev >> Subject: Re: Re: the error happend when use the healthcheck to get the >> status of upstrems. >> Thx. >> >> >> >> [email protected] >> >> From: YuanSheng Wang >> Date: 2020-04-02 11:58 >> To: [email protected] >> Subject: Re: Re: the error happend when use the healthcheck to get the >> status of upstrems. >> I do not know how to fix it yet. >> >> >> >> On Wed, Apr 1, 2020 at 10:47 PM [email protected] <[email protected]> wrote: >> >> > Is there any way to avoid this? >> > >> > >> > >> > [email protected] >> > >> > From: YuanSheng Wang >> > Date: 2020-04-01 22:43 >> > To: [email protected] >> > Subject: Re: the error happend when use the healthcheck to get the >> status >> > of upstrems. >> > That is a bug of lua-resty-healthcheck, here is the related issue [1]. >> > >> > It is not easy to fix it. >> > >> > [1] https://github.com/Kong/lua-resty-healthcheck/issues/36 >> > >> > >> > >> > On Wed, Apr 1, 2020 at 10:22 PM [email protected] <[email protected]> >> wrote: >> > >> > > I got the error when I use the healthcheck to get the status of >> upstrems. >> > > Has anyone ever had the same problem? >> > > >> > > Error: >> > > 2020/03/31 17:03:01 [error] 47#47: *128805375 failed to run >> > > balancer_by_lua*: /usr/local/openresty/lualib/resty/lock.lua:153: API >> > > disabled in the context of balancer_by_lua* >> > > stack traceback: >> > > [C]: in function 'sleep' >> > > /usr/local/openresty/lualib/resty/lock.lua:153: in function >> > 'lock' >> > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:207: >> in >> > > function 'locking_target_list' >> > > /opt/app/mecs//deps/share/lua/5.1/resty/healthcheck.lua:1315: >> in >> > > function 'new' >> > > /opt/app/mecs//lua/travelsky/http/checker.lua:25: in function >> > > 'create_obj_fun' >> > > /opt/app/mdcs//lua/apisix/core/lrucache.lua:50: in function >> > > 'lrucache_checker' >> > > /opt/app/mecs//lua/travelsky/http/checker.lua:35: in function >> > > 'fetch_checker' >> > > /opt/app/mecs//lua/travelsky/http/balancer.lua:221: in >> function >> > > 'pick_server' >> > > /opt/app/mecs//lua/travelsky/http/balancer.lua:287: in >> function >> > > 'load_balancer' >> > > /opt/app/mecs//lua/travelsky.lua:259: in function >> > > 'http_balancer_phase' >> > > balancer_by_lua:2: in main chunk while connecting to upstream, >> > > client: 101.5.19.12, server: , request: "POST / HTTP/1.1", host: " >> > > 101.5.19.15:8080" >> > > >> > > >> > > >> > > >> > > [email protected] >> > > >> > >> > >> > -- >> > *MembPhis* >> > My github: https://github.com/membphis >> > Apache APISIX: https://github.com/apache/incubator-apisix >> > >> >> >> -- >> *MembPhis* >> My github: https://github.com/membphis >> Apache APISIX: https://github.com/apache/incubator-apisix >> > > > -- > *MembPhis* > My github: https://github.com/membphis > Apache APISIX: https://github.com/apache/incubator-apisix > -- *MembPhis* My github: https://github.com/membphis Apache APISIX: https://github.com/apache/incubator-apisix
Re: [ANNOUNCE] new PPMC: sshniro
Congratulations. [email protected] From: Ming Wen Date: 2020-05-03 17:11 To: dev Subject: [ANNOUNCE] new PPMC: sshniro hello, community, The Project Management Committee(PMC) of Apache APISIX has vote passed and invited sshniro to be a PPMC. We are pleased to announce that he has accepted. sshniro, welcome to join Apache APISIX PPMC :) Thanks, Ming Wen, Apache APISIX & Apache SkyWalking Twitter: _WenMing
Re: Re: Support to import Open API specs to automatically create routes in APISIX [Discuss]
That's a good idea. [email protected] From: Zhiyuan Ju Date: 2020-05-14 17:37 To: dev Subject: Re: Support to import Open API specs to automatically create routes in APISIX [Discuss] Agree. APISIX should be as simple as possible, and because Swagger has fixed formats, so we could use js to parse the yml file, and then do a batch create to APISIX. Ming Wen 于2020年5月14日 周四下午5:35写道： > I think it may be more suitable as a separate tool, and it will be more > flexible. > How about add this parser tool in dashhaord? > > Thanks, > Ming Wen, Apache APISIX & Apache SkyWalking > Twitter: _WenMing > > > Nirojan Selvanathan 于2020年5月12日周二 下午5:13写道： > > > Hi All, > > > > Many use Open API specification to define the APIs. It would be nice if > we > > can support the feature > > to import the API specification and to automatically create routes based > on > > the specification. In case if we support this how can we implement this? > > > > - Feature as part of the Admin API? An upload Open API spec endpoint? > > - A separate script (probably python ?) to parse the swagger spec and > > create routes? > > > > Also, I assume we need to provide support for a route prefix when > importing > > the swagger specs. > > Would like to know your thoughts on this. > > -- > > Best Regards, > > S.Nirojan > > Linked-in <https://www.linkedin.com/in/niroselva/> > > > -- 来自 琚致远
Re: Re: [VOTE] Release Apache APISIX (Incubating) 1.3-RC2
+1 I checked: - incubating in name - download links are valid - signatures and hashes fine - DISCLAIMER is included - LICENSE and NOTICE good - no binary files - all source file have ASF headers - compiled and run on CentOS [email protected] From: junxu chen Date: 2020-05-16 19:02 To: dev Subject: Re: [VOTE] Release Apache APISIX (Incubating) 1.3-RC2 +1 I checked: - incubating in name - download links are valid - signatures and hashes fine - DISCLAIMER is included - LICENSE and NOTICE good - no binary files - all source file have ASF headers - compiled and ran quick start on macOS On Sat, May 16, 2020 at 6:36 PM wangzhiquan wrote: > +1 > > > > > -- 原始邮件 -- > 发件人: "jinwei" 发送时间: 2020年5月16日(星期六) 中午11:42 > 收件人: "dev" 抄送: "dev" 主题: Re: [VOTE] Release Apache APISIX (Incubating) 1.3-RC2 > > > > +1 > > > > > On 05/16/2020 11:26, Li Ling(Lien) wrote: > +1 > > I checked: > - incubating in name. > - Download links are valid. > - Checksums and PGP signatures are valid. > - DISCLAIMER is included. > > agile6v > > +1 > > > > I checked: > > - incubating in name. > > - Download links are valid. > > - Checksums and PGP signatures are valid. > > - DISCLAIMER is included. > > - LICENSE and NOTICE files are good. > > - No binary file. > > - All files have license headers if necessary. > > > > Regards, > > agile6v > > > > On 2020/05/13 14:07:48, Lang Wang > > Hello, Community, > > > > > > This is a call for the vote to release Apache APISIX > (Incubating) version > > > 1.3-RC2. > > > > > > > > > Release notes: > > > > > > > https://github.com/apache/incubator-apisix/blob/v1.3/CHANGELOG.md#130 > > > <https://github.com/apache/incubator-apisix/blob/v1.3/CHANGELOG.md#130>>; > > > > > > > > The release candidates: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/ > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/>>; > > > > > > > > Git tag for the release: > > > > > > https://github.com/apache/incubator-apisix/tree/v1.3 > > > > > > > > > Release Commit ID: > > > > > > > > > https://github.com/apache/incubator-apisix/commit/d947acf320b2cb0a76e62e92e686fe1a3dd1deee > > > <https://github.com/apache/incubator-apisix/commit/d947acf320b2cb0a76e62e92e686fe1a3dd1deee>>; > > > > > > > > Keys to verify the Release Candidate: > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS>>; > > > > > > > > Steps to validating the release: > > > > > > 1. Download the release > > > > > > ``` > > > > > > wget > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz > > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz>>; > > > > > ``` > > > > > > > > > 2. Checksums and signatures > > > > > > ``` > > > > > > wget > https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/KEYS>>; > > > > > wget > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz.asc > > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz.asc>>; > > > > > wget > > > > > > https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz.sha512 > > > <https://dist.apache.org/repos/dist/dev/incubator/apisix/1.3-rc2/apache-apisix-1.3-rc2-incubating-src.tar.gz.sha512>>; > > > > > shasum -c apache-apisix-1.3-rc2-incubating-src.tar.gz.sha512 > > > > > > gpg --import KEYS > > > > > > # input `trust`, `5`, then `save` > > > > > > gpg --edit-key "Lang Wang" > > > > > > gpg --verify apache-apisix-1.3-rc2-incubating-src.tar.gz.asc > > > apache-apisix-1.3-rc2-incubating-src.tar.gz > > > > > > ``` > > > > > > > > > 3. Unzip and Check files > > > > > > ``` > > > >
