a2aproject / a2aproject/a2a-python

[Bug]: `taskId` without `contextId` creates a new context instead of inheriting it

未關閉
#1,206 3 則留言 0 個 reaction 已指派 1 人 已被 @rohityan 認領 在 GitHub 檢視
component: server status:awaiting response status:stale
主要語言
Python
星號
2.1k
分支
496
平均合併
4 天 17 小時
30 天內合併 PR
12

描述

### What happened?

Spec:
> Agents MUST infer contextId from the task if only taskId is provided

Code:
```python
request_context = await self._request_context_builder.build(
params=params,
task_id=original_task_id,
context_id=original_context_id,
task=None,
context=call_context,
)
```

Then further...
```
if not self._context_id and not self._params.message.context_id:
self._params.message.context_id = self._context_id_generator.generate(...)
```

I found no sight of using the task's context, it seems to generate it anyway. But please correct me if I'm wrong.

### Relevant log output

```shell

```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

貢獻指南

開啟貢獻指南

評估

這個 Issue 還沒有評估資料。

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。