2.5 KiB
Prompt
Rebase PR #484 onto final PR #481, migrate every affected one-shot call to the new positional target API and continue through downstream tests, examples and documentation review.
Response summary
Converted stale target keyword calls to target partials so previously named inputs remain explicit while placement/runtime controls stay direct. Updated error expectations for local signature validation and linked remote error propagation, then corrected docs which still described the removed one-shot implementation. Linked spawning and context lifecycle prose to the corresponding API methods and detailed context guide.
Files changed
docs/api/core.rst- describe linked one-shot context execution.docs/guide/rpc.rst- update placement and target call semantics.docs/guide/spawning.rst- document positional target inputs.examples/debugging/multi_nested_subactors_error_up_through_nurseries.py- migrate nested actor target inputs.examples/debugging/root_cancelled_but_child_is_in_tty_lock.py- preserve named recursive target inputs with partials.tests/test_advanced_streaming.py- migrate streaming target inputs.tests/test_cancellation.py- migrate calls and tighten errors.tests/test_infected_asyncio.py- bind asyncio target options.tests/test_rpc.py- migrate RPC target argument binding.tests/test_runtime.py- preserve named runtime target inputs.tests/test_spawning.py- preserve named spawning target inputs.
Human edits
The human selected the stack order and final PR #481 base, asked the agent to continue after each diagnostic step and required a complete commit plan after independently force-pushing the rebased history. After reviewing the migration, the human required every formerly named target input to remain visibly named through functools.partial() rather than becoming positional. These were human-directed agent edits; the human also required plain start_actor() and open_context() references in the spawning and RPC guides to link to their API methods and the detailed context guide, then clarified that to_actor.run() already uses the full context API while Portal.run() should share linked lifecycle machinery without necessarily delegating through Portal.open_context() or adding a Started message. The human made no direct source-line edits.