Improve error message when sync actions timeout
Bug #1721571 reported by
Thomas Herve
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mistral |
Fix Released
|
Medium
|
Eyal B |
Bug Description
I run the following call on a mistral env:
$ mistral run-action std.sleep '{"seconds": 120}'
ERROR (app) MessagingTimeout: Timed out waiting for a reply to message ID 57979027948c4ed
I don't expect the call to work, as sync actions are inherently limited, but it'd be nice to have a more clear error message, so that it doesn't appear to be an infrastructure issue.
Changed in mistral: | |
status: | New → Triaged |
importance: | Undecided → Medium |
milestone: | none → queens-2 |
Changed in mistral: | |
assignee: | int32bit (int32bit) → nobody |
Changed in mistral: | |
milestone: | queens-2 → queens-3 |
Changed in mistral: | |
milestone: | queens-3 → rocky-1 |
Changed in mistral: | |
status: | In Progress → Triaged |
Changed in mistral: | |
milestone: | rocky-1 → rocky-2 |
Changed in mistral: | |
milestone: | rocky-2 → rocky-3 |
Changed in mistral: | |
milestone: | rocky-3 → stein-1 |
Changed in mistral: | |
milestone: | stein-1 → stein-2 |
Changed in mistral: | |
milestone: | stein-2 → stein-3 |
Changed in mistral: | |
milestone: | stein-3 → train-2 |
Changed in mistral: | |
assignee: | nobody → Eyal B (eyalb1) |
Changed in mistral: | |
status: | Triaged → In Progress |
Changed in mistral: | |
milestone: | train-2 → train-1 |
To post a comment you must log in.
So should we have any idea to exactly distinguish whether the exception is really an infrastructure issue or execution timeout ?