Keep member names with non-UTF-8 bytes distinct
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The payload names no files, so start by finding where member and loose-file names are decoded from bytes as UTF-8 with replacement. Read the review of #23 for the options raised. The first step is a maintainer decision on the key scheme (byte keys or a fixed decoding), not a code change. Done means that decision is recorded and a test shows two names differing only in invalid bytes stay distinct.
Written by the indexing model from the issue text.
Description
Member and loose-file names are decoded as UTF-8 with replacement, so two names that differ only in bytes that are not valid UTF-8 collapse into one, and neither can be requested by its real name. On macOS, a loose file whose name is stored in decomposed form (NFD) does not match the same name requested in composed form. No shipped file is affected; user-made content can be.
Options raised in the review of #23: byte keys that lower-case ASCII only, or one fixed decoding (such as Windows-1252) applied on both sides.
- Dominant language
- Rust
- Stars
- 0
- Forks
- 0
- Avg merge
- 1h 1m
- Merged PRs (30d)
- 128
Getting set up
- No Dockerfile or Docker Compose file
- No 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 RustyZoo/RustyZoo
-
original-bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
original-bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
original-bug
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
original-bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
-
original-bug
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 1 day
All issues in RustyZoo/RustyZoo
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
shep-pm/shep-kelpie#980 ·
Maintainers usually reply within 1 day
-
bug frontend rt sev-3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
C-bug
Difficulty 1/5 Under an hour Newbie friendliness 88/100
-
[1.x Bug] run-operation --sql reports success but rolls back writes on transaction-capable adaptersOpentriage
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
dbt-labs/dbt#16784 · 1 comment ·
Maintainers usually reply within 1 day
-
area:cli bug good first issue priority:medium
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day