CPLAT-8603 Add Multiple Error Check to ErrorBoundary

[joebingham-wk]

Motivation

Currently, an ErrorBoundary can be fooled to think that the UI is recoverable by a call stack varying even though the same two or three call stack repeatedly occurs.

Changes

• Keep track of all errors thrown in the same 5 second interval.

Release Notes

• Add ErrorBoundary fix that helps to prevent recovery attempts after the UI is unrecoverable.

Review

See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.

Please review:
@kealjones-wk @greglittlefield-wf @sydneyjodon-wk

QA Checklist

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Test in wdesk_sdk to ensure an infinite loop can no longer occur
    • Add a virtualized list as the content to a side panel element (I was using header_footer_properties_panel_content.dart). You can override that file with this gist that has a virtual list.
    • Override web_skin_dart and add an error that gets thrown on mount in RegionComponent
    • Override over_react with this branch
    • Run the wdesk_sdk app, clicking into a document, the side panel, and the second tab within the panel navigation. For the purposes of this test, the document should unmount and not enter an infinite loop. Removing the over_react override and doing the same test should result in an infinite loop
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Client Platform member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[greglittlefield-wf]

+1

Nice job on this implementation and tests!!

[greglittlefield-wf]

+10

@Workiva/release-management-p