When the message broker is not yet on, and the pipeline services try to contact it, they issue a unclosed socket warnings. See ampq.py
Expected Behavior
Close the socket properly if open and cannot connect.
Current Behavior
Issues a warning. I'm afraid it's wasting sockets (at the level of the OS).
Hopefully, it's a minor issue, cuz the (wasted) sockets will timeout and the OS will reclaim them.
Possible solution
Review the code by someone else with competence in socket in python (and/or OS).
When the message broker is not yet on, and the pipeline services try to contact it, they issue a
unclosed socket
warnings. See ampq.pyExpected Behavior
Close the socket properly if open and cannot connect.
Current Behavior
Issues a warning. I'm afraid it's wasting sockets (at the level of the OS). Hopefully, it's a minor issue, cuz the (wasted) sockets will timeout and the OS will reclaim them.
Possible solution
Review the code by someone else with competence in socket in python (and/or OS).