Progress spins forever on internal error
Opened this issue · 0 comments
mindplay-dk commented
Improve internal error-handling to prevent progress spinners that spin forever.
The case I encountered was a malformed JSON payload in X-ChromeLogger-Data, where an object was passed to table instead of an array, and thus failed to iterate.
Add error-handling to prevent this - basically catch errors while rendering legacy ChromeLogger data, stop the spinner and display an error message.