-
Notifications
You must be signed in to change notification settings - Fork 49
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
BagLinterTest fails under MacOs #102
Comments
I also run MacOs High Sierra 10.13.2 and it does not fail for me. How is your hard drive formatted? Mine is |
Indeed, this is strange. I'm using APFS (Unencrypted), too. Currently, I'm encrypting my filesystem to see if this has any influence, but I don't think so. Maybe the German system language causes this issue? I've played around a bit with ManifestChecker#checkNormalization and I found out, that during BagLintTest#testLintBag 'src/test/resources/linterTestBag/data/Núñez' is normalized to 'src/test/resources/linterTestBag/data/Nu´n~ez' unless I'm using Normalizer.Form.NFC Edit: Edit2: Ok, it seems that the different behaviour is indeed caused by the German locale settings. Obviously, NFD as well as NFC normalization have to be supported somehow. |
Do you still get this error if you change the |
Changing the locale in the code doesn't change anything. Also changing the system language to English has no influence. According to this article it seems that this issue is related to APFS and indeed, the colleague running her iMac with an English Locale is still not using High Sierra and therefore also no APFS but HFS+. However, the fact that the tests are succeeding on your machine running APFS is now even more confusing. |
What is the output from the
|
For me this looks quite similar:
|
Yeah doing a diff, the only difference is the size and UUIDs. I am running on a old macbook air, so I have upgraded several times. Did you always have APFS, or like me did you upgrade? |
I'm not totally sure, but I think that I've upgraded it with macOS High Sierra. |
Given
When
Then
Obviously, removing BagitWarning.DIFFERENT_NORMALIZATION from the list of expected warnings is not longer necessary.
The text was updated successfully, but these errors were encountered: