-
Notifications
You must be signed in to change notification settings - Fork 58
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
remove directory with weird mojibake encoding #183
Conversation
|
FWIW, the commit that created that is 270fa98 |
Codecov Report
@@ Coverage Diff @@
## master #183 +/- ##
==========================================
- Coverage 88.35% 88.29% -0.07%
==========================================
Files 33 33
Lines 3211 3211
==========================================
- Hits 2837 2835 -2
- Misses 374 376 +2
Continue to review full report at Codecov.
|
|
It seems no test tries to scan this folder anymore, and that the error on badly encoded path reappeared 😮 |
|
Ah, thanks for the follow up. Makes sense. Turns out one of our QA tool broke and this helped find a bug :) I do think generating that directory during the tests and cleaning it afterwards makes much more sense though, as a bunch of things don't like badly encoded paths. |
|
Thanks for merging this - it was causing me headaches when trying to develop on MacOS (Linux was fine) |
i have tried to convert a real, live workstation to ZFS and had to recreate all filesystems because of this silly settings. It actually failed to copy [source code from the supysonic project](https://github.com/spl0k/supysonic/tree/270fa9883b2f2bc98f1482a68f7d9022017af50b/tests/assets/%E6) (which was [eventually removed](spl0k/supysonic#183), but still). I don't think we should suggest such an advanced setting by default and, in general, I find that this guide suggests too many exotic things, instead of focusing on "just install the thing with ZFS".
I have tried to convert a real, live workstation to ZFS and had to recreate all filesystems because of this silly settings. It actually failed to copy [source code from the supysonic project][1] (which was [eventually removed][2], but still). This commit addresses *all* such incantations I could find, but keep a reference to it in the **Hints** section or, if it's not present, the **Notes** section, mentioning it was removed and why. This is so people *can* still add it if they want. [1]: https://github.com/spl0k/supysonic/tree/270fa9883b2f2bc98f1482a68f7d9022017af50b/tests/assets/%E [2]: spl0k/supysonic#183
I don't know how that directory was created (and it's been there for a year already...) but suddently my Debian QA tools freaked out on this weirdly encoded thing...
Bash also showed the char as
�/