-
-
Notifications
You must be signed in to change notification settings - Fork 35.4k
OS X 10.11: system calls return non-normalized unicode strings #2165
Copy link
Copy link
Closed
Labels
fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.macosIssues and PRs related to the macOS platform / OSX.Issues and PRs related to the macOS platform / OSX.testIssues and PRs related to the tests.Issues and PRs related to the tests.
Metadata
Metadata
Assignees
Labels
fsIssues and PRs related to the fs subsystem / file system.Issues and PRs related to the fs subsystem / file system.i18n-apiIssues and PRs related to the i18n implementation.Issues and PRs related to the i18n implementation.macosIssues and PRs related to the macOS platform / OSX.Issues and PRs related to the macOS platform / OSX.testIssues and PRs related to the tests.Issues and PRs related to the tests.
test/sequential/test-chdir.jspersistently fails on OS X 10.11 because the output ofprocess.cwd()doesn't match the path we're doingprocess.chdir()on before.Here's a reduced test case (
npm i mkdirp hexy):The strings look identical on the terminal, but the bytes differ. Here's the output:
cc: @evanlucas