mirror of
https://github.com/agentscope-ai/ReMe.git
synced 2026-10-14 04:12:05 +00:00
e4c381c7b1
benchmark.yaml's python_execute job advertised a `timeout` parameter, but `timeout` is one of the CLI's client-selection kwargs (reme/reme.py pops it before the payload is sent), so `reme python_execute code=... timeout=300` never delivered the timeout to the job. The value silently became the HTTP client's request timeout while the subprocess kept the 60s default, so benchmark code that needs longer was killed at 60s with no hint why. HTTP and MCP callers were unaffected. Rename the parameter to `python_timeout`, mirroring how the shell job already avoids the same collision with `shell_timeout`. The step prefers the new name and still accepts the legacy `timeout` context key so existing benchmark configs keep working. A new guard test fails if any job in reme/config/*.yaml or a plugin plugin.yaml declares a client-reserved parameter name again. |
||
|---|---|---|
| .. | ||
| __init__.py | ||
| add.py | ||
| app_config.py | ||
| chat.py | ||
| demo.py | ||
| health_check.py | ||
| help.py | ||
| llm_demo.py | ||
| python_execute.py | ||
| shell.py | ||
| status.py | ||
| stream_demo.py | ||
| stream_llm_demo.py | ||
| version.py | ||