Associate messages with Pipes in a "best effort" way about pynng HOT 3 CLOSED

nng calls the pipe callback directly, so it seems even likelier that this is a bookkeeping issue in pynng. See https://github.com/nanomsg/nng/blob/82afec95496fd2e4b8fb404aa90e961f93db1fe8/src/core/socket.c#L1439. I'm struggling to think of what the issue is.

from pynng.

There's a separate race condition where the message is received and then the pipe is disconnected from the socket that also needs to be protected against, but that's not the reason that the test failed in Travis.

from pynng.

Fixed in 586ae5e, but I'm not thrilled about it. At some level it's necessary because of the disconnect race condition, but I'm worried it will cover up other issues, so a logger.warning() is issued and CI runs will be verbose and won't capture stderr/stdout soon to see if the warning is ever seen.

from pynng.