A blocking call and a call that returns at once
Two timelines aligned at the request, on the kit clock. Track A: one blocking SendMessage for task 3d8f7801 stays open while the task passes TASK_STATE_SUBMITTED and TASK_STATE_WORKING, which the client never sees, and six artifact chunks arrive. The reply comes at TASK_STATE_COMPLETED, 09:00:00.750. Track B: SendMessage with returnImmediately for task d0c28826 returns at TASK_STATE_SUBMITTED, 09:00:01.000. A first GetTask sees TASK_STATE_WORKING at 09:00:01.250 with one log part, and a second GetTask sees TASK_STATE_COMPLETED at 09:00:01.500 with all artifacts.
A · BLOCKING
SendMessage with no configuration, task 3d8f7801
B · AT ONCE
returnImmediately, then GetTask twice, task d0c28826
TASK_STATE_SUBMITTED
TASK_STATE_WORKING
TASK_STATE_COMPLETED
KIT CLOCK
1
SendMessage, blocking: one reply, the completed task with test-log.txt and summary.json
2
SendMessage with returnImmediately: the reply holds TASK_STATE_SUBMITTED
3
GetTask, historyLength 0: TASK_STATE_WORKING and the first of five log parts
4
GetTask, historyLength 0: TASK_STATE_COMPLETED, five log parts, and summary.json
1
one request, held open until the reply
not seen
not seen
09:00:00.750
2
SendMessage
09:00:01.000
3
09:00:01.250
4
09:00:01.500