Add a CI check that no two paths collide on case-insensitive filesystems
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- bun, github-actions, typescript
- Domain
- build-system, ci-cd
Research direction
Read .github/workflows/validate.yml and inspect the existing bun validate checks to find where a path collision check belongs. Add a check that fails when paths or directories collide after lowercasing and prints both paths; done when validation catches the example collision and passes for unique paths.
Written by the indexing model from the issue text.
Description
The usual shape: two directories in the same place that differ only in case, e.g. .../qwen/ and .../Qwen/. On macOS (APFS is case-insensitive by default) they merge into one directory, and git status then reports the contents as a rename/move. On Linux both exist. Downstream (Nixpkgs), this sometimes hash mismatch issue since the source tree isn't the same between Linux and macOS.
Could we extend bun validate (already run by .github/workflows/validate.yml) with a check that every path plus every directory is unique when lowercased, failing with both offending paths printed.
- Dominant language
- TypeScript
- Stars
- 7.5k
- Forks
- 2k
- Avg merge
- 40m
- Merged PRs (30d)
- 916
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 anomalyco/models.dev
-
automation missing-model model-sync provider:morph
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#12536 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
anomalyco/models.dev#12471 ·
Maintainers usually reply within 1 day
-
automation missing-model model-sync provider:fireworks-ai
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
anomalyco/models.dev#12458 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/models.dev#12413 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
anomalyco/models.dev#11866 ·
Maintainers usually reply within 1 day
All issues in anomalyco/models.dev
Similar issues
-
Add: Yichang TVOpencheck:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
vtselect: data race in Tempo search tags APIs for invalid TraceQL queriesPossibly taken @Shubham19032004 claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
VictoriaMetrics/VictoriaTraces#304 ·
Maintainers usually reply within 1 day
-
test: claim-conflict drop leaves both facts active and is never re-proposed (untested review cell)Open
Difficulty 2/5 1-3 hours Newbie friendliness 83/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
microsoft/vscode-pull-request-github#9159 ·
Maintainers usually reply within 1 day
-
[Feature]: Usage page should show API-equivalent cost and say when a connected plan shows info onlyOpenenhancement from-x
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
nightly-labs/openbot#4867 ·
Maintainers usually reply within 1 day