`63c` and `63e` can never pass: run-by-name has no process serving the agent's workers

Open
#487 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
68/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
python
Domain
distributed-systems

Research direction

Start with examples/agents/63b_serve.py, 63d_serve_from_package.py, 63c_run_by_name.py, and 63e_run_monitoring.py, then check run_all_examples.py's DAEMON_SKIP entries. Choose either a working serve() pairing or documented separate serving commands, and run 63c with workers available to confirm it completes instead of hanging.

Written by the indexing model from the issue text.

Description

bug

Files: examples/agents/63c_run_by_name.py, examples/agents/63e_run_monitoring.py, examples/agents/63b_serve.py, examples/agents/63d_serve_from_package.py

Symptom: Both hang indefinitely (300s timeout, no output) on every server type.

Cause: runtime.run("doc_assistant", ...) runs an agent by name, so the client never sees the agent object and cannot start workers for its tools. The tool tasks are scheduled with nothing polling them:

task 'search_docs'  SCHEDULED in doc_assistant,  queue last polled 6005s ago   # 63c
task 'health_check' SCHEDULED in monitoring,     queue last polled 600s ago    # 63e

The examples meant to provide those workers cannot: 63b_serve.py and 63d_serve_from_package.py have every runtime.serve(...) call commented out — their executable bodies are a single runtime.run(...). So no shipped example serves workers for a named agent.

Fix: Either restore a working serve() in 63b/63d, or document that 63c/63e require a separate serving process and show the command. Any fix should make the pairing runnable end to end.

Verify: With the serving process running, python examples/agents/63c_run_by_name.py completes instead of hanging.

Related: run_all_examples.py's DAEMON_SKIP describes 63b/63d as "serve() worker daemon (blocks forever)". They are not daemons — both complete in ~3.4s. That skip entry is stale; 63c's ("needs 63b_serve.py workers running in another terminal") is accurate but unachievable as shipped.

Dominant language
Python
Stars
104
Forks
43
Avg merge
1d 13h
Merged PRs (30d)
4

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from conductor-oss/python-sdk

All issues in conductor-oss/python-sdk

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.