Repository navigation
os.hostname() return garbled code on windows if the host name contains non ascii characters #38255
Description
Activity
@addaleax @cjihrig I have fixed this locally and want to Push request. But I'm not sure about the stratagy of this PR, since the root cause is in deps/uv/src/win/util.c.
Should I push this to libuv/libuv first. And then merge the files back to deps/uv after the PR merged in libuv/libuv ?
Yes, you may make a PR at libuv with your change and once that lands, the code in Node.js too will be updated with your change when
deps/uvis upgraded with a new release.Reacted by Anna Henningsen and Benjamin Gruenbaum@Ayase-252 Can I make a PR to update
deps/uvfrom libuv as the my PR already be merged in it.
Because our project awaiting this update in nodejsNode.js will update
libuvdep whenlibuvreleases a new version in normal workflow. I'm not sure how to handle this case if the patch is urge for you.cc @cjihrig
Yes, we should wait for a new libuv release.
What steps will reproduce the bug?
ANDREW-ü-LAPTOPANDREW-�-LAPTOPHow often does it reproduce? Is there a required condition?
Always happen.
What is the expected behavior?
ANDREW-ü-LAPTOP
What do you see instead?
ANDREW-�-LAPTOP
Additional information
the fix of #27848 would work fine on linux/macOs. But on windows, libuv's implement does not decoding the string which return be windows API, which cause this bug.