opensource/dify
2
0
Fork 0
mirror of https://github.com/langgenius/dify.git synced 2026-05-09 12:59:18 +08:00
Code Issues Packages Projects Releases Wiki Activity

remove stale comments

Browse Source
This commit is contained in:
yunlu.wen 2026-04-21 17:50:37 +08:00
parent d226a5bdd3
commit 33db927327
1 changed files with 1 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
api/services/workflow_event_snapshot_service.py
View File

@ -73,17 +73,7 @@ def build_workflow_event_stream(
represents the history that already happened from the client's point of view.
2. Tail phase: events delivered by the broadcast subscription **from the moment of
subscription onward only**. Anything that was published before the subscription was
established is intentionally ignored here, because it has already been covered by
the snapshot phase.
The application layer does not use the broadcast channel's replay capability on any path
(see ``stream_topic_events``). Mixing replay with the snapshot produces events that
overlap along the history axis, and the frontend handlers are not idempotent across the
whole event set (string content is accumulated, ``workflow_paused`` re-opens a new SSE
subscription, iteration/loop starts and file entries are pushed into lists, etc.). A
future feature that wants to recover events published *after* the snapshot was read but
*before* this function subscribed should solve it at the subscription layer
(cursor/position) rather than by re-sending the historical prefix.
established is ignored here, since message id is not tracked in current implementation.
"""
topic = MessageGenerator.get_response_topic(app_mode, workflow_run.id)
workflow_run_repo = DifyAPIRepositoryFactory.create_api_workflow_run_repository(session_maker)