Nathan

request help: failed to connect to the unix socket through docker

8

After solved the issue [https://github.com/apache/apisix-java-plugin-runner/issues/156] I use docker-compose.yml which file is created by you to start apisix ``` sudo docker-compose -f ../ci/docker-compose.yml up -d ``` After that, apisix works. I...

Repeated sslhandshake in [tcp-log] plugin

2

### Is there an existing issue for this? - [X] I have searched the existing issues ### Kong version (`$ kong version`) master ### Current Behavior  I am developing...

In fact , redis cluster supports to **eval MORE THAN ONE keys** **via {}** use `{}` around keys to use Redis Key hash tags. Thus. This check logic is not...

ssl session repeated sslhandshake

2

branch : master https://github.com/openresty/lua-resty-websocket/blob/eba3e979620f847fc6bdb3f64e9adf86b59a0251/lib/resty/websocket/client.lua#L172 ``` if scheme == "wss" then if not ssl_support then return nil, "ngx_lua 0.9.11+ required for SSL sockets" end if client_cert then ok, err = sock:setclientcert(client_cert,...

Hi请教几个网络通信方面的问题

2

Hi bro. 已经把大佬的代码反复看了几遍，写的很优雅很棒。有几个地方想探讨一下 如图， a. 每次produce 消息的时候都new socket ,使用完成后不关闭而是setkeepalive，这样做是把tcp链接交给nginx管理，每次new的时候从nginx那边找到可用的链接，我的理解对吗，复用链接的时候会重复ssl handshake吗？ b. 如果是这样的话，如何解决僵尸链接的问题，比如server端已经挂了，客户端还是认为链接有效，导致消息发送失败，这样的情况可能发生吗 c. 每次发一条消息后，都要等server端ack后，才能发下一条，可以改成启动2个轻线程，发的时候push到queue里，由轻线程从queue里pop了发，另一个线程专门处理receive事件，这样做对消息量大的时候会不会效率更高呢？

OrderStatus应作为值对象

4

为何要把OrderStatus加上Id变成实体呢？

history_market_temperature接口总是返回空数组

1

**问题描述** history_market_temperature接口总是返回空数组 **代码例子** ```py from datetime import date resp = QuoteContext.history_market_temperature(Market.US, date(2024,1,1), date(2025,7,12)) print(resp) ``` **错误信息或结果截图** HistoryMarketTemperatureResponse { granularity: Unknown, records: [] } **你的环境信息** - 操作系统: [Windows] - 开发语言: Python...