Yichun Zhang
Yichun Zhang
@sergey-lukin I think you can just check out existing test cases in the `t/mock.t` test file. If you are unfamiliar with the test toolchain based on `Test::Nginx`, I suggest you...
@Samin-Du I've already been working on connection-pool-based concurrency level limiting of the underlying cosocket API in the `pool-limiting` branch of lua-nginx-module: https://github.com/openresty/lua-nginx-module/tree/pool-limiting The first step is to return an error...
@misiek08 I don't have the time to look into this and I'll rely on contributions :)
Yes. I have put this into my TODO list. This is indeed a good thing to have.
Guys, there are two pull requests implementing cluster-related features on the client side. Have you checked them out? See https://github.com/openresty/lua-resty-redis/pulls
@bk10287 Enable the nginx debugging logs and see what's happening under the hood.
@bk10287 You are not enabling debugging logs. Once enabled, you should see a ton of `[debug]` level log messages.
@ecaroth The suggestion goes to you as well. This way, you can see exactly what IP address and port number are used to connect.
@KSDaemon In your redis-cli example, you are using a string literal value instead of a number value. So why don't you just use a string value in Lua too? Lua's...
@zavada What nginx variable are you using for the "request time" field in your access log? Is it `$request_time`? If yes, then the time specified by the `$request_time` variable includes...