mirror of
https://gitee.com/wanwujie/sub2api
synced 2026-04-03 06:52:13 +08:00
The upstream v0.1.90 changed GetAccountConcurrencyBatch from individual Lua script calls (which swallowed per-account errors) to a Redis pipeline approach that propagates errors from rdb.Time() or pipe.Exec(). When the HTTP request context is cancelled (e.g., browser abort), the entire batch fails and the handler silently shows all concurrency as 0. Fix: use context.WithTimeout(context.Background(), 3s) for the Redis call so HTTP request cancellation doesn't affect the read-only concurrency query.