Commit fa1d994
committed
fix: Use createUserTextMessage for cloud deployment client
The cloud deployment test was using A2A.toUserMessage(text, id) which
sets the MESSAGE ID, not the TASK ID. This caused the "start" message
to have taskId=null, resulting in the error:
"Could not find a Task/Message for null"
Changes:
1. Changed sendStartMessage() to use createUserTextMessage(text, contextId, taskId)
This properly sets taskId instead of messageId
2. Added TimeoutException catch for consumptionFuture.get() timeout
The "process" and "complete" messages already used Message.builder()
with .taskId() so they were correct.
Fixes cloud-deployment example test.1 parent ed3ca50 commit fa1d994
File tree
2 files changed
+14
-7
lines changed- examples/cloud-deployment/server/src/test/java/io/a2a/examples/cloud
- server-common/src/main/java/io/a2a/server/requesthandlers
2 files changed
+14
-7
lines changedLines changed: 2 additions & 1 deletion
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
153 | 153 | | |
154 | 154 | | |
155 | 155 | | |
156 | | - | |
| 156 | + | |
| 157 | + | |
157 | 158 | | |
158 | 159 | | |
159 | 160 | | |
| |||
Lines changed: 12 additions & 6 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
609 | 609 | | |
610 | 610 | | |
611 | 611 | | |
612 | | - | |
| 612 | + | |
613 | 613 | | |
614 | | - | |
615 | | - | |
| 614 | + | |
616 | 615 | | |
617 | 616 | | |
618 | 617 | | |
619 | | - | |
620 | | - | |
| 618 | + | |
| 619 | + | |
| 620 | + | |
| 621 | + | |
| 622 | + | |
| 623 | + | |
| 624 | + | |
| 625 | + | |
621 | 626 | | |
622 | 627 | | |
623 | 628 | | |
| |||
629 | 634 | | |
630 | 635 | | |
631 | 636 | | |
632 | | - | |
| 637 | + | |
| 638 | + | |
633 | 639 | | |
634 | 640 | | |
635 | 641 | | |
| |||
0 commit comments