Date: Sun, 14 Oct 2018 13:07:22 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 232246] devel/py-oslo.messaging: Fix for the RabbitMQ driver when used with Python 3+ Message-ID: <bug-232246-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D232246 Bug ID: 232246 Summary: devel/py-oslo.messaging: Fix for the RabbitMQ driver when used with Python 3+ Product: Ports & Packages Version: Latest Hardware: Any OS: Any Status: New Severity: Affects Only Me Priority: --- Component: Individual Port(s) Assignee: sunpoet@FreeBSD.org Reporter: freebsd_ports@k-worx.org CC: python@FreeBSD.org, sunpoet@FreeBSD.org Flags: maintainer-feedback?(sunpoet@FreeBSD.org) Assignee: sunpoet@FreeBSD.org Attachment #198134 maintainer-approval?(sunpoet@FreeBSD.org) Flags: CC: sunpoet@FreeBSD.org Created attachment 198134 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D198134&action= =3Dedit py-oslo.messaging-fix-rabbitmq-py36.patch Hello, attached is the patch that fixes the RabbitMQ driver (=3D oslo_messaging/_drivers/impl_rabbit.py) on FreeBSD when used as Python 3+ package. Without the patch the RabbitMQ messaging driver tries to use a timeout for a newly created TCP socket but will fail shortly afterwards because FreeBSD doesn't implement the TCP_USER_TIMEOUT option (RFC 5482) (yet?). This leads into spawning multiple embryonic TCP connections that are never going into the ESTABLISHED state.=20 The issue has been discovered during runtime-tests of the misc/py-cinder po= rt in conjunction with a RabbitMQ messaging server. Please see also the attach= ed logfile for further details. QA: ~~~ - poudriere (10.4-, 11.2-RELEASE, 12.0-ALPHA9 amd64 + i386) for each py27 + py36 flavor -> OK - portlint -> OK --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-232246-21822>