-
Notifications
You must be signed in to change notification settings - Fork 6
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
Incompatibility with Windows OS #66
Comments
Does this only happen when cloning / forking the repository? Did they try to disable the warning with If we are providing the raw (original) files of these collections, then this may not be solvable. From the link you provided:
If the original collections include these files, then we can consider doing some cleaning, as long as this does not interfere with our pipelines. |
Errors only happen when cloning the repository (both using git and Github Desktop). Disabling the warning only excludes the errors listed at point 1. This problem does not seem to be solvable, and a cleaning on our side seems to be necessary. I asked the validator for a copy of the error log so that we can study the problem in more detail. |
Here the error log:
|
Thanks, so it is clear that all this mess come from the jungle of Wikifonia and iReal forum dump. For Wikifonia, it seems not to like the I have the feeling that these question marks already come from encoding issues (e.g. non UTF stuff) 🤔 |
I think the cleanest and most sustainable thing would be to write a script that renames files containing question marks (very simply based on the Unix An integration with GitHub Actions might be a solution, so that an automatic check (and possibly file renaming) is done every time a commit is made on the main branch. |
Can be the easiest solution, as long as these question marks are not hiding some encoding issues. In |
In 5725112 a script named TODO: add a GitHub action that runs such script according to certain parameters (e.g. push tags). |
Testers (validators) report that there are problems cloning and working with the ChoCo repository due to some naming conventions in the subfolders of
partitions
.More specifically, these errors refer to:
?
).The use of Docker containers can solve this problem for end users.
However, the problem of reproducibility of the results on non-UNIX-based environments and the potential expansion of the community of contributors behind the ChoCo project remain.
The text was updated successfully, but these errors were encountered: