Conversation
With caching disabled, the eviction after a quiescent activation forced a shutdown boundary before input readiness could arrive, then repeated it on every replacement task. Core now waits for the boundary, as it does for local Activities.
This was referenced Oct 3, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR keeps a retained external stream task alive until its boundary when the workflow cache is off.
What changed?
ManagedRun::retains_task_for_external_streamssays whether a run still holds its task for external streams, either for a quiescent wait or for buffered output.Part of AI-198 (epic AI-37).
Why?
Python tests and harness workers often run with caching off. There the eviction forced a shutdown boundary before input readiness could arrive, and then did it again on every replacement task, so the run looped on markers and never read its records. Evicting at the task's normal boundary fixes it.
How did you test it?
Link to a test plan if any -
Two cases run with a zero-sized cache: a retained stream task accepts readiness and leaves the cache only after its boundary, and a task holding buffered output stays until the flush. The whole Core lib suite passes, and the lints and fmt are clean.