Long ty names written to disk can leak username info in paths
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Long ty names written to disk also has this issue
Originally posted by @jieyouxu in https://github.com/rust-lang/rust/issues/128594#issuecomment-2266659008
When a type error contains a long type name, it can be written to disk. However, sometimes these long type names can contain username info or absolute paths.
cc #128914 as this may be of concern.
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
The issue identifies long type names written to disk as potentially exposing usernames or absolute paths, but names no files, tests, or entry points. Begin by locating the compiler code that persists long type names and review issue #128914 for related context; done means the persisted output no longer leaks this path information and the behavior is covered by a regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100