5 Commits

Author	SHA1	Message	Date
juju	9c31b0ca95	fix: Fixed the bug where the bus was closed and consumers had unfinished messages. (#1179) ... * fix: Fixed the bug where the bus was closed and consumers had unfinished messages. * fix: remove unnecessary blank line in Close method * fix: refactor message bus and channel handling for improved performance and reliability * fix: improve message handling and bus closure logic for better reliability * fix: reduce sleep duration in agent loop for improved responsiveness * fix the test case	2026-03-18 00:12:12 +08:00
Petrichor	62bdece7f5	chore: resolve conflicts with upstream/main	2026-02-28 12:21:54 +08:00
Hoshina	ba98069a00	fix: resolve wastedassign lint warnings in channel subpackages ... Remove wasted initial assignments before switch statements in onebot (segType), telegram (filename), and wecom (mediaType).	2026-02-26 23:36:06 +08:00
Hoshina	72e897f95a	fix(channels): fix memory hazards in channel abstraction layer ... Address 7 memory/architecture issues affecting long-running gateway processes on embedded devices (<10MB RAM): - Fix dispatcher busy-wait: remove select+default pattern that caused CPU spin after context cancellation; SubscribeOutbound handles ctx internally - Add TTL janitor for typingStops/placeholders sync.Map entries to prevent unbounded accumulation when outbound paths fail - Reduce queue buffers from 100 to 16 slots (~84% memory reduction) - Optimize SplitMessage with index-based rune operations to reduce intermediate string/rune allocations - Replace uuid.New() with atomic counter + random prefix for media scope IDs (eliminates per-call crypto/rand syscall) - Lazy channel worker creation: defer goroutine+buffer allocation until channel.Start() succeeds	2026-02-24 22:30:22 +08:00
Hoshina	afc7a1988f	refactor(bus): fix deadlock and concurrency issues in MessageBus ... PublishInbound/PublishOutbound held RLock during blocking channel sends, deadlocking against Close() which needs a write lock when the buffer is full. ConsumeInbound/SubscribeOutbound used bare receives instead of comma-ok, causing zero-value processing or busy loops after close. Replace sync.RWMutex+bool with atomic.Bool+done channel so Publish methods use a lock-free 3-way select (send / done / ctx.Done). Add context.Context parameter to both Publish methods so callers can cancel or timeout blocked sends. Close() now only sets the atomic flag and closes the done channel—never closes the data channels—eliminating send-on-closed-channel panics. - Remove dead code: RegisterHandler, GetHandler, handlers map, MessageHandler type (zero callers across the whole repo) - Add ErrBusClosed sentinel error - Update all 10 caller sites to pass context - Add msgBus.Close() to gateway and agent shutdown flows - Add pkg/bus/bus_test.go with 11 test cases covering basic round-trip, context cancellation, closed-bus behavior, concurrent publish+close, full-buffer timeout, and idempotent Close	2026-02-23 00:44:45 +08:00