-
-
Notifications
You must be signed in to change notification settings - Fork 24.7k
fix: target the correct HIL action when clearing pending messages #6615
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
sanahkapoor
wants to merge
1
commit into
FlowiseAI:main
Choose a base branch
from
sanahkapoor:bugfix/hil-action-target-wrong-node
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+105
−16
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| import { findChatMessageActionToClear } from './buildAgentflow' | ||
| import { ChatMessage } from '../database/entities/ChatMessage' | ||
|
|
||
| const makeMessage = (id: string, action: object | null): ChatMessage => { | ||
| const message = new ChatMessage() | ||
| message.id = id | ||
| message.action = action ? JSON.stringify(action) : null | ||
| return message | ||
| } | ||
|
|
||
| describe('findChatMessageActionToClear', () => { | ||
| it('returns the message whose action.data.nodeId matches the resumed startNodeId', () => { | ||
| const messages = [ | ||
| makeMessage('msg-3', { data: { nodeId: 'humanInput_2' } }), | ||
| makeMessage('msg-2', { data: { nodeId: 'humanInput_1' } }), | ||
| makeMessage('msg-1', null) | ||
| ] | ||
|
|
||
| const result = findChatMessageActionToClear(messages, 'humanInput_1') | ||
|
|
||
| expect(result?.id).toBe('msg-2') | ||
| }) | ||
|
|
||
| it('does not clear a different pending Human-In-The-Loop node just because it is newer (#4787)', () => { | ||
| // Two HIL nodes are pending at the same time. Resuming humanInput_1 must not touch | ||
| // the chat message that belongs to humanInput_2, even though it was created more recently. | ||
| const newerUnrelatedAction = makeMessage('msg-newer', { data: { nodeId: 'humanInput_2' } }) | ||
| const olderTargetAction = makeMessage('msg-older', { data: { nodeId: 'humanInput_1' } }) | ||
| const messages = [newerUnrelatedAction, olderTargetAction] | ||
|
|
||
| const result = findChatMessageActionToClear(messages, 'humanInput_1') | ||
|
|
||
| expect(result?.id).toBe('msg-older') | ||
| expect(result?.id).not.toBe(newerUnrelatedAction.id) | ||
| }) | ||
|
|
||
| it('returns undefined when no message matches the startNodeId', () => { | ||
| const messages = [makeMessage('msg-1', { data: { nodeId: 'humanInput_2' } })] | ||
|
|
||
| const result = findChatMessageActionToClear(messages, 'humanInput_1') | ||
|
|
||
| expect(result).toBeUndefined() | ||
| }) | ||
|
|
||
| it('returns undefined when startNodeId is not provided', () => { | ||
| const messages = [makeMessage('msg-1', { data: { nodeId: 'humanInput_1' } })] | ||
|
|
||
| const result = findChatMessageActionToClear(messages, undefined) | ||
|
|
||
| expect(result).toBeUndefined() | ||
| }) | ||
|
|
||
| it('skips messages with malformed action JSON instead of throwing', () => { | ||
| const malformed = new ChatMessage() | ||
| malformed.id = 'msg-malformed' | ||
| malformed.action = '{not valid json' | ||
|
|
||
| const valid = makeMessage('msg-valid', { data: { nodeId: 'humanInput_1' } }) | ||
|
|
||
| const result = findChatMessageActionToClear([malformed, valid], 'humanInput_1') | ||
|
|
||
| expect(result?.id).toBe('msg-valid') | ||
| }) | ||
|
|
||
| it('skips messages with no action set', () => { | ||
| const messages = [makeMessage('msg-1', null), makeMessage('msg-2', { data: { nodeId: 'humanInput_1' } })] | ||
|
|
||
| const result = findChatMessageActionToClear(messages, 'humanInput_1') | ||
|
|
||
| expect(result?.id).toBe('msg-2') | ||
| }) | ||
| }) |
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
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
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Issue: Potential incorrect matching or runtime errors when comparing action IDs
There are two main concerns with the current comparison logic:
undefined: If bothmsg.actionandactionare objects but neither has anidproperty (or if they are both strings, making.idevaluate toundefined),msg.action.id === action.idwill evaluate totrue(sinceundefined === undefinedistrue). This can cause the wrong message's action to be cleared.msg.actionandactioncan be either a JSON string or a parsed object. If one is a string and the other is an object, comparing.iddirectly will fail to match.Recommendation
Implement a robust helper to safely extract the action ID, handling both stringified and parsed object formats, and explicitly verify that both IDs are defined before comparing them.
References