You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit bcbfbde
Browse filesBrowse the repository at this point in the historyBrowse files
fix(harness): keep a protocol's own exception type in the coordinator record (R3)
Review (zengchuang-hw, 096f93c): when a frozen optimization.py raised in
its `arguments` operation, coordinator-error.json recorded type
"TaskProtocolError" instead of the protocol's own type, which the
in-process call recorded before R3. The settlement reason on that path
was and stays the existing coordinator behaviour, "ValueError: <message>".
- TaskProtocolError gains `type_name`: the protocol's own exception type
for kind protocol_exception, "TaskProtocolError" for every other kind.
It replaces the `reason` attribute added in 096f93c.
- optimization._type_name() feeds both _failure and
coordinator-error.json, so all three operations leave the records
they left before R3.
- New regression drives `session start` and a real `round` with an
`arguments` TypeError: coordinator-error.json is
{"type": "TypeError", "error": "bad arguments"}, the attempt settles
as "ValueError: bad arguments" and the benchmark never starts.
- CHANGELOG states the record per operation instead of one broad claim.
Refs #412
Agent-assisted-by: Claude Code / claude-opus-5-5 [effort=xhigh] (author)
Signed-off-by: GUOGUO <xwdong1998@163.com>
0 commit comments