)]}'
{"mistral/engine/post_tx_queue.py":[{"author":{"_account_id":11583,"name":"Arnaud Morin","email":"arnaud.morin@gmail.com","username":"arnaudmorin"},"change_message_id":"22370b353adeebf14c25c2d974d08463830398a0","unresolved":true,"context_lines":[{"line_number":110,"context_line":"            # retrying forever on a connection that cannot be established,"},{"line_number":111,"context_line":"            # which otherwise hangs the process at shutdown, waiting for"},{"line_number":112,"context_line":"            # the thread to die)."},{"line_number":113,"context_line":"            t \u003d threading.Thread(target\u003d_within_new_thread, daemon\u003dTrue)"},{"line_number":114,"context_line":"            t.start()"},{"line_number":115,"context_line":"        finally:"},{"line_number":116,"context_line":"            _clear()"}],"source_content_type":"text/x-python","patch_set":1,"id":"c73615ad_48165bf8","line":113,"updated":"2026-10-16 14:21:04.000000000","message":"I am affraid this is going to change the behavior of mistral under restart. If an action was ongoing (like a db write to set the workflow in RUNNING and start a new exectution), this may be killed abrupty and leave the execution in a middle.\nCan we instead try to figure out which tests are sending messages on the transport and configure the fake transport for them instead of waiting for kombu to retry indefinitely?","commit_id":"1353a48d0803e0a0666e569f9a1861f260362d20"}]}
