During a boardwalkd server update I noticed that a running instance of the boardwalk CLI crashed because the server was temporarily serving 503 errors while the server updated to the new version. The crash occurred as a result of polling for the workspace catch, and there was also a stacktrace emitted by the unmutex attempt which also received a 503.
This update should make the CLI tolerant of this kind of server error
How was this tested?
Tested by manually manipulating boardwalkd locally to cause 503s to be produced during initial CLI connections, and while the CLI is polling for a remote catch. It appears to handle this kind of error more gracefully now.
Checklist
[x] Have you updated the VERSION file (if applicable)?
What and why?
During a boardwalkd server update I noticed that a running instance of the boardwalk CLI crashed because the server was temporarily serving 503 errors while the server updated to the new version. The crash occurred as a result of polling for the workspace catch, and there was also a stacktrace emitted by the unmutex attempt which also received a 503.
This update should make the CLI tolerant of this kind of server error
How was this tested?
Tested by manually manipulating boardwalkd locally to cause 503s to be produced during initial CLI connections, and while the CLI is polling for a remote catch. It appears to handle this kind of error more gracefully now.
Checklist