Message bundle loading causing global failures in CI test environment

[nwhittaker]

Check existing issues

• I have checked for existing issues to avoid duplicates

Actual Behavior

About 50% of our CI test runs fail with many could not fetch component message bundle errors. The suspicion is that some tests finish quickly and disconnect transient Calcite elements from the DOM before the elements are done hydrating.

Expected Behavior

Message bundle loading is canceled or does not throw after an element is disconnected. If the element is reconnected, perhaps throw then, or retry loading the message bundle.

Reproduction Sample

https://github.com/ArcGIS/acadia-web

Reproduction Steps

Unable to reproduce locally.

Reproduction Version

2.13.2

Relevant Info

Linux, x64, Chrome

Chrome flags

--no-sandbox: null
--headless
--crash-dumps-dir=/tmp
--disable-dev-shm-usage
--disable-gpu
--disable-software-rasterizer
--mute-audio
--remote-debugging-port=0
--window-size=1440,900

Stack trace

global failure: Error: could not fetch component message bundle
Error: could not fetch component message bundle
    at i (https://localhost:41529/calcite-components-2.13.2/p-3a1a720c.js:6:328)
    at https://localhost:41529/calcite-components-2.13.2/p-3a1a720c.js:6:291

Regression?

No response

Priority impact

impact - p3 - not time sensitive

Impact

A workaround for Field Apps is to swallow the error in QUnit's onUncaughtException handler. It's also possible this becomes a non-issue for us after upgrading to Calcite 3.

Calcite package

• @esri/calcite-components
• @esri/calcite-components-react
• @esri/calcite-design-tokens
• @esri/calcite-ui-icons
• @esri/eslint-plugin-calcite-components

Esri team

ArcGIS Field Apps