When using socket paths containing non-ASCII characters (i.e. Cyrillic) in ipc:// socket paths, the socket opening may fail.
This seems to happen because Windows expects UDS paths encoded in utf-8, however 'narrow' versions of file manipulation functions (like rmdir(), unlink(), etc) expect the local system code page.
When using socket paths containing non-ASCII characters (i.e. Cyrillic) in
ipc://
socket paths, the socket opening may fail.This seems to happen because Windows expects UDS paths encoded in
utf-8
, however 'narrow' versions of file manipulation functions (likermdir()
,unlink()
, etc) expect the local system code page.Environment