[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title Michael Neale updated an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Change By: Michael Neale Priority: Major Minor Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title James Dumay commented on JENKINS-42921 Re: Error "toast" popup for unhandled errors on the client to do with fetching 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! Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Change By: James Dumay Issue Type: Improvement Bug Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Change By: James Dumay Priority: Minor Major Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title James Dumay updated an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Change By: James Dumay Sprint: Blue Ocean 1.1 Add Comment This message was sent by Atlassian JIRA (v7.3.0#73011-sha1:3c73d0e) -- You received this message because you are subscribed to the Google Groups "Jenkins Issues" group. To unsubscribe from this group and stop receiving emails from it, send an email to jenkinsci-issues+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[JIRA] (JENKINS-42921) Error "toast" popup for unhandled errors on the client to do with fetching
Title: Message Title Michael Neale created an issue Jenkins / JENKINS-42921 Error "toast" popup for unhandled errors on the client to do with fetching Issue Type: Improvement Assignee: Unassigned Components: blueocean-plugin Created: 2017/Mar/20 4:39 AM Labels: technical-debt Priority: Minor Reporter: Michael Neale 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. cc James Dumay do you still think this is a good idea? Add Comment
