As it stands, we currently hammer the service's update logs endpoint in a tight loop while waiting for a deployment to complete. This is not necessary, and can indeed be deletrious to the user experience: it appears that this may be exacerbating some mysterious 500 responses from API gateway. These changes add a brief sleep in the relevant loop that waits for 5 seconds if the last call produced new log entries or 15 seconds if it did not. Fixes #844. |
||
---|---|---|
.. | ||
cloud | ||
local | ||
state | ||
backend.go | ||
display.go | ||
stack.go | ||
updates.go |