jeremyjpj0916

@chaitanya14 I added a unit test but I am not sure if I setup hostname correctly so docker could do FDQN to IP resolution correctly. Does this look right or...

I also added an enhancement that should allow us to resolve hostnames if IP is not specified similar to how Kong deals in DNS: https://github.com/dream11/kong-scalable-rate-limiter/pull/17 cc @chaitanya14 @chirag-manwani

@chirag-manwani It would be helpful to have a toggle bool setting that if redis unavailable to allow to fall back on local rate limiting mode(this way yourself + existing users...

typing on iphone so sorry for mistakes: 1. Non successful delivery of data to redis or a read from redis that failed. 2. Yes, I think code needs to retry...

1. Configurable count of failures but I would say default to 1 failure when this feat. is enabled but allows any int. 2. I would say it should check every...

Seems 3.7.x is imminent to fix the postgres TLS issues, see here for a possible workaround too: https://github.com/Kong/kong/issues/12702#issuecomment-2136370793

This an issue in 3.7.0 too? I think I have a custom plugin that used kong.db.* so this may be problematic for me too if it is the case. But...

Maybe this was plays a role? ``` - name: KONG_LUA_SOCKET_POOL_SIZE value: "30" ``` I noticed default is 256 w Kong. Not sure why I had it so low but just...

Not confirmed yet but will let yall know. testing out that change now. I run traditional mode here so no DP/CP setup at all.

@StarlightIbuki nope it still an issue even bumping that to 256: ``` 2024-06-20T23:44:08.208226437-05:00 nginx: [warn] the "user" directive makes sense only if the master process runs with super-user privileges, ignored...