How to pass through stdout?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 697
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
We have a bunch of images that need to be pushed to a registry so often, so we do them all in one big script. Problem is Gitlab's container registry constantly fails all the time so loop is a perfect fit for this.
Trying something like:
loop -s --summary -- scripts/push-images.sh (tried with -i as well)
But the problem is that there is zero output.
Whereas normally our scripts/push-images.sh outputs something like:
Pushing registry.gitlab.com/thing:prod
The push refers to repository [registry.gitlab.com/thing]
8850e5e866c3: Preparing
6d1eb370deee: Preparing
e6a9e93f2e3d: Preparing
f721b22510f1: Preparing
371e12a4bca7: Preparing
c97278a08a46: Preparing
7bff100f35cb: Preparing
c97278a08a46: Waiting
And updates as the scripts progress through each image.
Is there anyway to keep that stdout and print it to term live as loop receives it from the subprocess?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with loop -s --summary -- scripts/push-images.sh and the referenced scripts/push-images.sh, comparing its normal terminal output with the looped command. Trace how loop receives and handles subprocess output. Done means stdout from the subprocess is displayed live in the terminal while the script runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100