Skip to content

Progress spins forever on internal error #5

@mindplay-dk

Description

@mindplay-dk

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions