kshitijk4poor
f3add023c2
fix(yuanbao): pop tracking entries only for truthy matching msg_id + regression tests
...
Follow-up on the salvaged pair: the original guard's `not msg_id` arm let an
id-less internal/synthetic event erase a tracking entry a concurrently-queued
id-bearing message's drain task still needs for recall matching (id-less
events never write entries in _dispatch_inbound_event, so they must never
pop). Tests cover: normal cleanup, id-less non-erasure, overwritten-entry
ownership handoff, TTL eviction + fresh-entry survival.
2026-08-03 17:33:14 +05:30
..
2026-07-05 06:29:26 -07:00
2026-04-28 09:50:27 -07:00
2026-08-03 17:33:14 +05:30
2026-08-01 18:42:53 -07:00
2026-05-12 17:08:51 -07:00
2026-08-02 10:02:33 -07:00
2026-06-28 02:05:50 -07:00
2026-08-02 15:08:45 -07:00
2026-06-24 04:16:54 +05:30
2026-07-29 11:53:39 -07:00
2026-07-04 13:28:47 -07:00
2026-07-24 15:47:12 -07:00
2026-07-24 15:55:08 -07:00
2026-07-24 15:47:12 -07:00
2026-07-23 11:34:11 -07:00
2026-06-29 12:18:11 -07:00
2026-06-07 19:16:36 -07:00
2026-08-02 23:17:40 +05:30
2026-07-28 22:41:09 -07:00
2026-05-16 12:55:23 -07:00
2026-06-16 15:49:59 -07:00
2026-07-05 14:01:03 -07:00
2026-08-02 10:02:33 -07:00
2026-08-01 15:34:19 -07:00
2026-07-15 09:50:05 -07:00
2026-07-24 15:55:08 -07:00
2026-07-26 16:55:42 -07:00
2026-07-01 02:48:36 -07:00
2026-08-03 09:57:58 +05:30
2026-06-30 15:30:06 -07:00
2026-08-03 17:17:28 +05:30
2026-08-03 17:16:57 +05:30
2026-06-24 18:47:18 -07:00
2026-08-03 00:25:20 +05:30
2026-08-02 16:16:36 -07:00
2026-07-29 12:11:15 -07:00
2026-08-03 17:31:29 +05:30
2026-07-29 16:45:35 +05:30
2026-07-24 11:45:57 -07:00
2026-07-28 22:41:09 -07:00
2026-05-10 12:33:54 -07:00
2026-08-02 00:11:50 -07:00
2026-07-05 06:29:26 -07:00
2026-07-29 23:16:18 -07:00
2026-05-19 00:12:41 -07:00
2026-08-01 10:51:55 -07:00
2026-06-02 00:33:50 -07:00
2026-06-02 00:33:50 -07:00
2026-07-28 22:31:40 -07:00
2026-07-18 20:01:55 +05:30
2026-08-02 14:23:55 +05:30
2026-07-19 03:49:29 -07:00
2026-07-23 11:55:17 -07:00
2026-06-28 02:05:26 -07:00