Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

Runtime does not start workers for tools declared on a `planner=` agent

Aperta Adatta ai principianti
  • Qualcosa non va?
#478 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
82/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Tranquilla
Stack tecnologico
python
Ambito
backend, distributed-systems

Direzione di ricerca

Inizia da src/conductor/ai/agents/runtime/runtime.py, concentrandoti su come vengono raccolti gli strumenti del worker per un agent e i suoi slot planner= e fallback=. Riproduci il problema con examples/agents/86_coding_agent.py e verifica che raggiunga il planner invece di rimanere bloccato; l’errore successivo "No JSON plan found" è un difetto separato.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug

In short: an agent passed as planner= gets no workers started for its tools, so its tasks sit in the queue with nothing polling them and the example hangs forever.

Files: src/conductor/ai/agents/runtime/runtime.py; reproduced by examples/agents/86_coding_agent.py

Symptom

$ python examples/agents/86_coding_agent.py

Hangs forever, no output after the worker banner. Output at 180s and 300s is byte-identical — no progress. Still reproduces on Orkes Conductor 5.5.0 against main at 8ff5f88f (240s, no progress).

Cause

Workers start only for the parent agent's tools=. Tools declared on the agent passed as planner= get none, so the planner's read_file tasks stay SCHEDULED with nothing polling them.

  • grep -n '\.planner' runtime.py matches only comments — no code reads that slot when collecting worker tools.
  • _ensure_models_for_agent walks a.agents recursively, so the old form was covered.
  • The named slots planner= / fallback= replaced the older agents=[planner, fallback] form, and the traversal was never extended to them.

Fix

Collect worker tools through planner= and fallback=, not only agents=.

Verify

python examples/agents/86_coding_agent.py reaches the planner and stops hanging. Confirmed: supplying those four workers from a second process ends the hang (128s vs indefinite).

Notes

This does not make 86 pass. It then fails with No JSON plan found and no fallback agent configured, a separate defect.

Reproduce on Orkes Conductor 5.5.0, not OSS 3.32.0. On OSS 3.32.0 the example no longer reaches this hang — it fails first, at 42s, with a separate defect that masks this one:

Plan compilation failed: Validation 0 has unsafe success_condition:
unexpected trailing input: '('passed') >= 0' at position 9 in: $.indexOf('passed') >= 0

No other example is known to expose this. 115_plan_execute_planner_context.py and adk/24_planner.py both use planner= but cannot reach it, and both pass:

  • 115's planner declares the same four tools as its parent harness, so the parent's tools= already starts those workers.
  • adk/24_planner.py passes BuiltInPlanner(...), which carries no tools at all.
Lingua principale
Python
Stelle
104
Fork
44
Merge medio
4g 18h
PR unite (30g)
3

Preparare l'ambiente

  • Include un Dockerfile o un file Docker Compose
  • Nessun modello di pull request
  • Nessuna guida per i contributori

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di conductor-oss/python-sdk

Tutte le issue di conductor-oss/python-sdk

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.