Refactor message handling for improved streaming and event management#1349
Refactor message handling for improved streaming and event management#1349trheyi merged 1 commit intoYaoApp:mainfrom
Conversation
trheyi
commented
Nov 26, 2025
- Updated message structures to replace 'StreamStartData' and 'StreamEndData' with 'EventStreamStartData' and 'EventStreamEndData' for better clarity and consistency.
- Introduced 'EventMessageStartData' and 'EventMessageEndData' to represent individual message lifecycle events, enhancing the granularity of message tracking.
- Refactored the 'streamState' and 'groupTracker' to utilize the new message structures, improving the organization and handling of streaming events.
- Enhanced the context management by integrating an ID generator for unique message identifiers, facilitating better tracking of message sequences.
- Updated documentation and tests to reflect the new message structures and ensure proper functionality across the system.
- Updated message structures to replace 'StreamStartData' and 'StreamEndData' with 'EventStreamStartData' and 'EventStreamEndData' for better clarity and consistency. - Introduced 'EventMessageStartData' and 'EventMessageEndData' to represent individual message lifecycle events, enhancing the granularity of message tracking. - Refactored the 'streamState' and 'groupTracker' to utilize the new message structures, improving the organization and handling of streaming events. - Enhanced the context management by integrating an ID generator for unique message identifiers, facilitating better tracking of message sequences. - Updated documentation and tests to reflect the new message structures and ensure proper functionality across the system.
|
Thank you for the PR! The db: SQLite3 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL8.0 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 5 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: SQLite3 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: SQLite3 redis: 4 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
Thank you for the PR! The db: MySQL5.7 redis: 6 mongo: 6.0 test workflow is running, the results of the run will be commented later. |
|
✨DONE✨ db: SQLite3 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: SQLite3 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 4 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL5.7 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 5 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 6 mongo: 6.0 passed. |
|
✨DONE✨ db: MySQL8.0 redis: 4 mongo: 6.0 passed. |