Thijs Schreijer
Thijs Schreijer
ah, but the method is available. Sockets are just transparent wrappers around luasocket sockets, so it should have it. Just isn't documented.
oops... you're right. looked at the close method, but indeed the shutdown is missing. My bad.
see https://github.com/brunoos/luasec/issues/181
for now I just updated all to 'close', not perfect but will do I guess.
@Python1320 The main "connect" problem is here; https://github.com/xHasKx/luamqtt/blob/master/mqtt/luasocket.lua#L12 It uses `socket.connect` shortcut, which is blocking without a timeout. Can be circumvented easily by using code like this; ```lua local sock...
@marc-charpentier 👏 👏 👏 > A reason to cache DNS entries in L1 only may be that a same service/target may resolve to different IPs on a round-robin basis, or...
Shouldn't we be fixing the underlying problem with `kong.log` to also provide the proper namespace when in a timer context? @kikito any opinions? iirc you were involved when `kong.log` was...
@ADD-SP is this something we can fix with the timer-ng lib?
@fffonion I don't think this can be done, for the reasons you found out. I discussed it with @bungle as well for Vaults and other pieces that need it as...
`lua-resty-aws` and `lua-resty-gcp` both use LuaSocket fallbacks as well. Not sure how that works/fails with the current Vaults solution.