Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Case-sensitive file conflict in repository causes issues on case-insensitive filesystems #6970

Open
2 tasks done
czareko opened this issue Dec 20, 2024 · 2 comments · May be fixed by #6981
Open
2 tasks done

Case-sensitive file conflict in repository causes issues on case-insensitive filesystems #6970

czareko opened this issue Dec 20, 2024 · 2 comments · May be fixed by #6981
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@czareko
Copy link

czareko commented Dec 20, 2024

Is there an existing issue?

  • I have searched the existing issues

Experiencing problems? Have you tried our Stack Exchange first?

  • This is not a support question.

Description of bug

The repository contains files with names differing only in letter casing (e.g., ErrorTester.ts and errorTester.ts). This causes issues when cloning or working with the repository on case-insensitive filesystems such as macOS (default APFS) and Windows.

It comes from this change: #6728

Steps to reproduce

  1. Clone the repository on a case-insensitive filesystem (e.g., macOS or Windows).
  2. Observe the following warning:

warning: the following paths have collided (e.g. case-sensitive paths on a case-insensitive filesystem) and only one from the same colliding group is in the working tree: 'substrate/frame/revive/rpc/examples/js/abi/ErrorTester.ts' 'substrate/frame/revive/rpc/examples/js/abi/errorTester.ts'

@czareko czareko added I10-unconfirmed Issue might be valid, but it's not yet known. I2-bug The node fails to follow expected behavior. labels Dec 20, 2024
@bkchr
Copy link
Member

bkchr commented Dec 20, 2024

CC @pgherveou

But @czareko feel free to open a pr that fixes this.

@pgherveou
Copy link
Contributor

Sorry about that , let me just push a PR that rename them

@pgherveou pgherveou linked a pull request Dec 23, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I2-bug The node fails to follow expected behavior. I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants