Skip to content

Share subprocess request dispatch without changing message support - #73290

Open
ephraimbuddy wants to merge 1 commit into
apache:mainfrom
astronomer:subprocess-dispatch-registry
Open

ephraimbuddy wants to merge 1 commit into
apache:mainfrom
astronomer:subprocess-dispatch-registry

Conversation

@ephraimbuddy

Copy link
Copy Markdown
Contributor

Task supervision and Dag processing duplicate their message dispatch logic. Move dispatch to WatchedSubprocess, with an explicit supported message set for each subprocess and common requests delegated to request_handlers.py.

Preserve existing wire responses, error categories, serialization options, and process-specific behavior. Typed registration checks message/handler compatibility, method lookup honors overrides, and an explicit sentinel marks responses already sent.

Add parity tests for the exact supported message sets and shared handler reuse, alongside dispatch regression tests and negative typing cases.

This is a narrower alternative to #68106, with the same goal of sharing dispatch.


Was generative AI tooling used to co-author this PR?
  • Yes — Codex (GPT-6)

Generated-by: Codex (GPT-6) following the guidelines

Task and Dag subprocesses duplicate dispatch plumbing, making their supported message boundaries and shared behavior harder to keep aligned. Keep those boundaries explicit and protect the existing wire behavior as handlers evolve.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant