Current behavior
A device command calling that stuck for 4 days without finishing, could kill the whole alabOS due to rabbitmq exception.
Current solution is to set consumer_timeout to a very large number, but more elegant solution is available, just require tests:
https://chatgpt.com/share/69167464-45a8-800c-b706-75d2376fbab3
Expected Behavior
Should not die at any duration of runtime
Minimal example
TODO, set consumer_timeout to very small and run alabOS
Relevant files/images/logs
No response
Current behavior
A device command calling that stuck for 4 days without finishing, could kill the whole alabOS due to rabbitmq exception.
Current solution is to set consumer_timeout to a very large number, but more elegant solution is available, just require tests:
https://chatgpt.com/share/69167464-45a8-800c-b706-75d2376fbab3
Expected Behavior
Should not die at any duration of runtime
Minimal example
TODO, set consumer_timeout to very small and run alabOS
Relevant files/images/logs
No response