fix: prevent __start__ node from glowing when not active#77
Merged
cristipufu merged 1 commit intomainfrom Feb 18, 2026
Merged
Conversation
The __start__ node was incorrectly glowing alongside the actual active node because: (1) early WS events (__start__ started) were missed due to the backend starting execution before the frontend WS subscription was active, and (2) a prev===null fallback unconditionally added __start__ to matchIds. - Remove the prev===null block that added __start__ to matchIds for all first events, which caused it to get isExecutingNode=true - Seed activeNodes from historical REST state events in applyRunDetail so subsequent WS events have proper prev context Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
__start__node glowed alongside the actual active node (e.g.,coordinator,pipeline)prev: nullwhich triggered a fallback that added__start__to the glow setprev === nullfallback block in GraphPanel that unconditionally added__start__tomatchIdsapplyRunDetailso subsequent WS events have properprevcontextTest plan
🤖 Generated with Claude Code