[zeromq-dev] Assertions after migrating to python3.11

[Doug Meyer]

Dear ZMQ Folks,

We have recently migrated from python3.5.2/pyzmq20.0.0/libzmq4.3.3 to
python3.11.0/pyzmq25.0.0/libzmq4.3.4. This is running on Ubuntu 16.04.g LTS
with Linux 4.19.

This particular part of our system is a set of services which publish and
subscribe to messages. all of those messages are published into a message
"manager" service. The manager is the zmq.ROUTER, and the
publishers/subscribers are zmq.DEALERs.

The python3.5.2/pyzmq20.0.0/libzmq4.3.3 config has been nice and stable for
several years.

After the migration to python3.11.0/pyzmq25.0.0/libzmq4.3.4, we are
observing occasional aborts of our manager service. We see messages such as
these:

Mar 11 05:07:34 [...]: Assertion failed: false (src/object.cpp:170)


Mar 23 06:57:10 [...]: Assertion failed: ok (src/mailbox.cpp:99)


We spent a bit of time eb searching for these kinds of assertions. We noted
some activity back in 2019 associated with the Erlang bindings, but
otherwise we're not finding anything that seems specific to the Python
binding, but the search goes on.

We are wondering if you may have experience with this already and/or have
thoughts and suggestions on what we might look at or where you suspect the
issue may lie.

We'd be very thankful for any help you can offer.

Blessings,
Doug Meyer
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.zeromq.org/pipermail/zeromq-dev/attachments/20230406/396933a2/attachment.htm>