[Bug/Assistance]os任务进度一直为0

[shirly35]

Describe the bug
main分支，按照readme的步骤拉起来docker服务后，执行"python -m src.client.agent_test --config configs/agents/api_agents.yaml --agent vllm-14b"正常对话。下一步执行python -m src.assigne没有进度，agent也没有调通。结果如下：

Desktop (please complete the following information):

• OS: [e.g. Ubuntu 22.04]
• Python: [e.g. 3.9]

[Mountain-w]

src\client\task.py
worker["status"] 和 WorkerStatus.ALIVE.name 的类型不一致，做下兼容就行

[mkimhi]

I suspect this is caused by a controller port mismatch in the FC (AgentRL) setup. The stack uses an AgentRL controller on :5020, but the default assignment definition points TaskClient to , so sees zero workers and appears stuck.

I opened PR #215 to add an FC assignment preset ( + ) that uses , plus a README note and a clearer warning when the controller is unreachable.

[mkimhi]

I suspect this is caused by a controller port mismatch in the FC (AgentRL) setup. The extra/docker-compose.yml stack uses an AgentRL controller on :5020, but the default assignment definition points TaskClient to http://localhost:5000/api, so src.assigner sees zero workers and appears stuck.

I opened PR #215 to add an FC assignment preset (configs/assignments/default_fc.yaml + definition_fc.yaml) that uses http://localhost:5020/api, plus a README note and a clearer warning when the controller is unreachable.

[mihuuu]

遇到同样的问题，请问怎么解决呢？我只想跑 os task，用的是 gpt-4o-mini，系统是 MacOS

docker compose -f extra/docker-compose.yml up -d controller os_interaction-std redis

python -m src.assigner --config configs/assignments/os_gpt4o_mini.yaml