Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

xargs: Error: Command could not be run: The filename or extension is too long. (os error 206)

Open
#160 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
52/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Quiet
Tech stack
rust

Research direction

Start by reproducing the reported Windows command with find, xargs -0, and grep, comparing the default invocation with xargs -0 -n 1. Investigate how xargs determines the command-line limit and batches input on Windows. Done means the command no longer fails with OS error 206 while preserving correct batching and matching behavior.

Written by the indexing model from the issue text.

Description

The command I ran:

find src -name "*.json" -print0 | xargs -0 grep "centoscript-transform-named-subexpression" | cat

Apparently xargs doesn't know the real command line length limit

Trying to workaround resisted; I finally burned CPU by running

find src -name "*.json" -print0 | xargs -0 -n 1 grep "centoscript-transform-named-subexpression" | cat

Dominant language
Rust
Stars
5.2k
Forks
107
Avg merge
2d 19h
Merged PRs (30d)
4

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from microsoft/coreutils

All issues in microsoft/coreutils

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.