uucore: translations not found in `findutils` (and probably other projects)
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 24.1k
- Forks
- 2k
- Avg merge
- 1d 5h
- Merged PRs (30d)
- 365
Description
I noticed in findutils that the update to uucore 0.11.0 breaks a test (see https://github.com/uutils/findutils/actions/runs/34085599515/job/101628921985?pr=858):
thread 'find::matchers::tests::build_top_level_matcher_perm_bad' (4939) panicked at src/find/matchers/mod.rs:1743:13:
assertion failed: e.to_string().contains("invalid operator")
And when running the corresponding command from the test:
$ cargo run -q --bin=find find -perm foo
find: mode-error-invalid-operator
The key mode-error-invalid-operator is used in src/uucore/src/lib/features/mode.rs.
It looks like the translations of uucore are not found in findutils, even though they are in the crate: https://crates.io/crates/uucore/0.11.0/code/locales/en-US.ftl
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.
Research direction
Start by reproducing the failing findutils test and inspect src/uucore/src/lib/features/mode.rs, especially the mode-error-invalid-operator key. Trace why the translations in locales/en-US.ftl are not found from findutils. Done means the translated error is returned and the build_top_level_matcher_perm_bad assertion passes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli, localization
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100