openclaw - 💡(How to fix) Fix [Bug]: openclaw message send can hang indefinitely with no internal timeout, ignores parent SIGTERM [1 comments, 2 participants]

• Consider emitting a clear terminal error when delivery exceeds timeout, instead of spinning indefinitely.

TL;DR

Add an internal request timeout to the openclaw message send CLI and ensure it responds to SIGTERM to prevent indefinite hangs.

Guidance

• Implement a default internal request timeout of 30 seconds in the openclaw message send CLI to prevent prolonged execution.
• Modify the CLI to respond promptly to SIGTERM signals, allowing external supervisors like timeout to effectively terminate it.
• Consider adding a feature to emit a clear terminal error when delivery exceeds the timeout, providing feedback instead of spinning indefinitely.
• Use timeout -s KILL as a temporary workaround to ensure cron jobs do not consume excessive CPU resources.

Example

No code snippet is provided as the issue does not imply a specific code change, but rather a design or configuration adjustment.

Notes

The solution requires modifications to the openclaw message send CLI, which may involve changes to its underlying implementation or configuration. The exact steps for implementing these changes are not specified in the issue.

Recommendation

Apply a workaround by using timeout -s KILL with the openclaw message send CLI until an internal request timeout is implemented, to prevent CPU consumption and potential gateway/agent pileups.