im_server

Files

T

Austin 5dd0a42002 fix: harden message seq allocation against stale redis replicas

- use sentinel failover client for group message runtime when
  sentinel_master_name/sentinel_addrs are configured, so seq counter
  reads never hit a stale replica after failover
- re-seed missing redis seq counter from DB topic seqid instead of
  trusting the caller in-memory baseline
- on unique-key conflict during async persist, re-allocate seq from DB
  latest, bump redis counter and fix the idempotency record so resends
  with the same client mid return the final seq
- add uk(topic, seqid) unique keys for im_messages in tenant DDL

2026-09-15 12:41:38 +08:00

mock_store

feat: add IM service health and metrics endpoints

2026-09-09 14:24:40 +08:00

types

feat(群组): 添加群组解散状态支持与过滤逻辑

2026-09-14 20:06:41 +08:00

config_cache.go

feat: centralize app release configuration

2026-09-12 17:07:49 +08:00

group_message_runtime_test.go

fix: harden message seq allocation against stale redis replicas