-
Notifications
You must be signed in to change notification settings - Fork 24
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
Need help to checkout, corupt data? #120
Comments
Hello @Slashdacoda ! I've just tried and have seen no problem:
What's your OS and version of git? You can always try with the zip, you might be luckier, e.g.: wget https://github.com/kermitt2/entity-fishing/archive/refs/heads/master.zip |
Hey @kermitt2 A bit troubleshooting: After updating to 2.31.1 (https://gitforwindows.org), still same in git bash: After installing Cygwin 2.905 (64 bit):
Some character problem. In my case the msg is: The fix should be related to some path related character, maybe:
why this |
Update: on other pc with windows 10 it works, thats wierd^^ Never the less, i will try this steps to fix my enviroment: https://brendanforster.com/notes/fixing-invalid-git-paths-on-windows/ |
kermitt2#120 -> try to fix
kermitt2#120 -> try to fix
Ok, after all, the problem semes to be the last point in the name of the files. My enviroment can't find the 2 files with this nameshema. I figure it out at the point on recommiting the changed filename: A posible solution is renaming it without a dot at the end of the name. Following this propose i ask myself if
|
Hello ! The data you are pointing to come from an external evaluation corpus "Wikipedia" created by:
and they use the Wikipedia article name as file name - bad practice for file portability, but it's not our choice. The file names are referenced in I guess there is no problem to rename these files (this corpus is not very useful beyond old system comparison, and is not updated), just be sure to rename them also in the corresponding |
…indows enviroment
The checkout problem should be fixed, thx for the support @kermitt2 |
The text was updated successfully, but these errors were encountered: