tiennm99 97f376025d fix(modules): reserve reply budget and cap price-fetch timeouts in stats handlers ...

Stats handlers reused the single bounded update context for both upstream
price fetches and the final Telegram reply, while per-upstream HTTP timeouts
equalled the whole-handler budget. One slow upstream drained the deadline and
the reply failed with "context deadline exceeded" (observed on /stock_stats).

- add chathelper.FetchContext: fetches run under a child context that reserves
  a tail of the deadline for the reply, which is sent on the original context
- cap kbs/coin/gold/vnappmob HTTP timeouts at 3s so one hung upstream cannot
  consume the reply budget
- fetch held stock/coin prices concurrently (bounded) so total latency tracks
  the slowest single fetch instead of their sum; per-symbol failures degrade to
  a "no price" line and the summary still sends

2026-06-25 14:07:59 +07:00

..

chathelper_test.go

fix(modules): reserve reply budget and cap price-fetch timeouts in stats handlers

2026-06-25 14:07:59 +07:00

chathelper.go

fix(modules): reserve reply budget and cap price-fetch timeouts in stats handlers

2026-06-25 14:07:59 +07:00