wc: unexpected stdout diff for multi-file output padding
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 55/100
Research direction
Start by locating the rshell wc command entry point and any existing tests covering multi-file output. Reproduce the discrepancy with multi-file input and compare stdout with GNU wc, focusing on count-column width when filenames and a total line are printed. Done means the numeric counts, ordering, and byte-for-byte padding match GNU output.
Written by the indexing model from the issue text.
Description
Summary
QA comparison found that rshell's wc output column padding differs from GNU wc for multi-file input. The numeric counts and file ordering match, but the stdout differs byte-for-byte because GNU pads count columns more widely.
Sanitized example
Command shape:
find <directory> -type f | sort | xargs wc -l
rshell stdout excerpt:
19 <path>
19 <path>
19 <path>
91 <path>
122 <path>
114 <path>
69 <path>
19 <path>
27 <path>
20 <path>
27 <path>
22 <path>
27 <path>
19 <path>
27 <path>
18 <path>
27 <path>
19 <path>
27 <path>
21 <path>
27 <path>
21 <path>
27 <path>
19 <path>
GNU/oracle stdout excerpt:
19 <path>
19 <path>
19 <path>
91 <path>
122 <path>
114 <path>
69 <path>
19 <path>
27 <path>
20 <path>
27 <path>
22 <path>
27 <path>
19 <path>
27 <path>
18 <path>
27 <path>
19 <path>
27 <path>
21 <path>
27 <path>
21 <path>
27 <path>
Expected
wc should match GNU wc output formatting for multi-file counts, including the leading column padding used when filenames and a total line are printed.
Notes
This report is sanitized: it omits local artifact paths, run identifiers, and scenario-specific metadata. The finding was deduplicated across the QA run before filing.
- Dominant language
- Go
- Stars
- 31
- Forks
- 3
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 14
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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
DataDog/rshell#522 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Boolean flags accept --flag=value, diverging from GNU (only df rejects it)May be free again @julesmcrt claimed this 101 days ago, and no pull request is open. Open
DataDog/rshell#538 · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Maintainers usually reply within 1 day
Similar issues
-
self-host checker: E021 bound check reads an untyped literal at i32, not the type the call bindsOpen
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
JakeChampion/lang#11055 ·
Maintainers usually reply within 1 day
-
priority: low status: ready for dev
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hyperledger-labs/fabric-smart-client#2033 ·
Maintainers usually reply within 1 day
-
agent-butler-finding agent-research bug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
jordansmall/spindrift#4249 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
acceptance-tests phase-coding schema-coverage testing triaged
Difficulty 2/5 1-2 days Newbie friendliness 84/100
elastic/terraform-provider-elasticstack#5053 ·
Maintainers usually reply within 1 day