feat(pipeline-run): stream execution logs#39
Open
arseniy-pplx wants to merge 1 commit into
Open
Conversation
Add --stream to tangle sdk pipeline-runs logs to follow container logs live instead of fetching a one-shot snapshot. Opening the stream has its own bounded retry budget for transport errors and retryable 5xx responses, spent before the first line is yielded. An established stream is never reopened, so output cannot be duplicated; mid-stream drops, open failures, BrokenPipe and Ctrl-C all exit without tracebacks.
arseniy-pplx
marked this pull request as ready for review
July 20, 2026 18:10
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.
Summary
--streamtotangle sdk pipeline-runs logsfor live container-log followingContext
The existing command fetches a one-shot log snapshot. Long-running pipelines require users and automation to poll repeatedly. A follow mode provides the expected log-debugging workflow while keeping retry semantics explicit and bounded: only the initial open is retried, so an interrupted stream is never silently resumed with duplicated lines.
Testing
uv run pytest tests/test_client.py tests/test_pipeline_runs_cli.pyuvx ruff checkon the touched source filesuv lock --checkgit diff --check