tr: unexpected stderr diff when head truncates pipeline
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Needs clarification
- Activity status
- Quiet
- Domain
- cli, operating-systems
Research direction
Start with the representative pipeline cat /var/log/containers/* 2>/dev/null | tr -d '\r' | tr -s ' ' | head -n 160 and inspect the retained QA artifacts for invocation inv-20260518T234915.836852464Z-e8e540e3. Determine whether the broken-pipe stderr is expected for tr, then establish whether the desired result is suppression, documented divergence, or a harness/oracle change.
Written by the indexing model from the issue text.
Description
Summary
tr produced an unexpected rshell/oracle stderr diff candidate during agentic QA. When a downstream head truncates the pipeline, rshell reports broken-pipe write errors from tr; the oracle exits successfully with matching stdout and no stderr.
Run Context
- QA run id:
run-20260518T233741Z-tr - Target builtin:
tr - Scenario(s): 50 generated KIND scenarios (names omitted from this public body)
- Rshell commit/version:
unknown - Artifact reference: representative invocation
inv-20260518T234915.836852464Z-e8e540e3
Command
cat /var/log/containers/* 2>/dev/null | tr -d '
' | tr -s ' ' | head -n 160
Observed Difference
- Differing dimension:
stderr - Rshell exit code:
0 - Oracle exit code:
0 - Rshell stdout summary: stdout matched the oracle output
- Oracle stdout summary: stdout matched the rshell output
- Rshell stderr summary: emitted two
tr: write error: write |1: broken pipelines - Oracle stderr summary: empty stderr
Notes
This is an unexpected diff candidate from the QA harness. Full local artifacts are retained in the QA workspace. Maintainer judgment is still needed to decide whether rshell should suppress expected broken-pipe write errors for tr, document an intentional divergence, or adjust the harness/oracle comparison.
- Dominant language
- Go
- Stars
- 31
- Forks
- 3
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 11
Contributor guide
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.
More from DataDog/rshell
-
QA
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 84/100
-
enhancement needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
kind/cleanup
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
kubernetes-sigs/kueue#15947 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
sympozium-ai/sympozium#627 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100