Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-42921

Error "toast" popup for unhandled errors on the client to do with fetching (500 error class) with opt out

    XMLWordPrintable

    Details

    • Similar Issues:
    • Epic Link:

      Description

      It may make sense to capture fetch errors that are otherwise "dropped on the floor" and show it as a toast error message (with ability to find more details). 

       

      This should only be done if we know all places that errors are dropped are actual bugs. If there are cases where dropped errors on fetch (eg 404) are normal cases (ie no test results when opening test tab) then that should be fixed as part of the scope of this. 

       

      In scope: 

      • Allow consumers of fetch to opt out of errors for cases like 40x (so they aren't logged, or displayed)
      • Allow showing of error to the user 

       

      cc James Dumay do you still think this is a good idea? 

       

        Attachments

          Issue Links

            Activity

            Hide
            jamesdumay James Dumay added a comment -

            I think this is a very good idea and should be one of the first we pick up considering the state of error handling. Will be good to identify annoying toasts!

            Show
            jamesdumay James Dumay added a comment - I think this is a very good idea and should be one of the first we pick up considering the state of error handling. Will be good to identify annoying toasts!

              People

              Assignee:
              Unassigned Unassigned
              Reporter:
              michaelneale Michael Neale
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: