You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Reported in pyzmq, but after updating to libzmq 4.3.5, it appears the patch in #4422 did not fix the problem, but just shifted the error.
Environment
libzmq version (commit hash if unreleased): 4.3.5
OS: Windows 11 and 10
Python 3.12.3 via Microsoft Store (though others may be relevant)
There seems to be some interaction with VPNs or firewalls or something that has yet to be fully understood, making it very hard to reproduce. It appears to be most of the time for affected users, but I've never been able to see it myself.
I managed to reproduce this on the same system in the same env by adding a user with the username 日本語. So something in wepoll or libzmq (or Windows itself) is doing something weird that's sensitive to the username and/or home directory.
#4732 fixes one cause of this error, but not all. This error is indeed seen when _wmkdir raises, which is fixed by #4732, but the more mysterious case seen in pyzmq appears to be caused even after a successful bind of the ipc socket, which I can't explain.
Issue description
Reported in pyzmq, but after updating to libzmq 4.3.5, it appears the patch in #4422 did not fix the problem, but just shifted the error.
Environment
There seems to be some interaction with VPNs or firewalls or something that has yet to be fully understood, making it very hard to reproduce. It appears to be most of the time for affected users, but I've never been able to see it myself.
Minimal test code / Steps to reproduce the issue
Python:
What's the actual result? (include assertion message & call stack if applicable)
If built with cmake defaults (epoll, ipc enabled), this crashes with:
epoll.cpp:73
What's the expected result?
it doesn't crash.
The text was updated successfully, but these errors were encountered: